Tell me more ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 0 down vote favorite

I'm trying to connect to db using any-db module using following code:

pool = anyDB.createPool(dbURL, {min: 20, max: 100, onConnect: function (conn, done) { console.log("connected!"); done(null, conn) }});

It worked once, I started to write some more code and when I ran it again nothing happened. Literally - nothing. Server didn't give me any output. I checked if my postgres was still running, but it was ok. So I changed dbname in dbURL to see if any error will appear, but still got nothing. Then I turned postgres off aaaaand nodejs still didnt produce any error when I launched an application with it.

So my question is how is it possible and what should I do with it? :)

P.S.

I tried to use pure pg and got all the same story. Modules I installed: pg and any-db. Postgres works alright, sending queries through pgadmin3 works just fine. My system is linux mint 14, nodejs0.8.22 was compiled from sources, i tried 0.6 from repo - still nothing, so it's not node either.

Any help would be much appreciated! Thanks in advance! :)

share|improve this question
Are you sure you're not trying to use an asynchronous API in a synchronous way? – robertklep Mar 7 at 20:59
well, i assume onConnect should be called after connection has established. And i think even if i was using api in a wrong way, an error would still appear if i try to connect to a nonexisting db – gavlig Mar 7 at 21:07
True, although I wouldn't be surprised if the pool is lazily implemented and will only connect when there's an actual connection needed (like performing a query). – robertklep Mar 7 at 21:11

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.