Error: getaddrinfo ENOTFOUND (postgres hostname with port) #355

Activity

1. pensierinmusica commented on Oct 13, 2013

   

   pensierinmusica

   on Oct 13, 2013

   More actions

   👍

   Please fix it :)
2. dresende

   added a commit that references this issue on Oct 14, 2013

   Fixes connection strings being parsed by url module to don't forget a…

   ...

   c7e914a
3. dresende commented on Oct 14, 2013

   

   dresende

   on Oct 14, 2013

   Owner

   More actions

   Please test this commit.

   npm install dresende/node-orm2
4. pensierinmusica commented on Oct 14, 2013

   

   pensierinmusica

   on Oct 14, 2013

   More actions

   Hi Diogo, thanks for the fix, it seems to work fine now!

   The npm package still needs to be updated though :)

   Please let me know when it's all done, so I can use the latest version. Thanks
5. dresende commented on Oct 14, 2013

   

   dresende

   on Oct 14, 2013

   Owner

   More actions

   Done. 2.1.3 in npm now.
6. dresende

   closed this as completedon Oct 14, 2013
7. nurrony commented on Dec 2, 2013

   

   nurrony

   on Dec 2, 2013

   More actions

   found same problem still using 2.1.3 here is my code

      var dbport = _dbConfig.port !== '' ? (':'+_dbConfig.port) : ''
       ,_dbDSN =  'mysql://'+_dbConfig.username+':'+_dbConfig.password+'@'+_dbConfig.host + dbport +'/'+_dbConfig.dbname;  
   
       app.use(orm.express(_dbDSN, {    
           define: function (db, models,next) {
               db.use(paging);
              _.each(dbSchema,function(structure, tblname){
                models[tblname] = db.define(tblname,structure);
              });
              //
              if(_dbConfig.sync){
                db.sync( function (err) {
                   !err && console.log("Database Tables Created Successfully!");
                });
              }   
              next();  
           }         
       })); 
   

   Throwing Same error like above, But it is resolved when i pass my db credentials as object not as string.
   Am i Doing wrong before.. or still a bug? confused
8. lewisoaten commented on Dec 3, 2013

   

   lewisoaten

   on Dec 3, 2013

   More actions

   This could be by design. I solved it by URL encoding my connection string.