On 9-4-2012 13:42, Dmitry Yemanov wrote: > 09.04.2012 15:24, Mark Rotteveel wrote: > >> Ok, then I need to get digging why some of the event related embedded >> tests are failing. I had ignored them previously because of this >> stackoverflow post: >> http://stackoverflow.com/questions/4438451/how-to-use-events-on-an-embedded-firebird-database-connection > > A second connection is just an implementation artifact of the remote > protocol, it has no relation to the events API itself.
I added a comment to the post so future readers are aware of this. I also found the problem after I shutdown my local Firebird server: the event manager in Jaybird was connecting to the server and not to embedded. The first two tests worked because they tested waiting for no events (with and without timeout), the other tests failed because embedded could not connect to the database file as it was already in use by the server (because the thread waiting for events was connected through superserver). -- Mark Rotteveel ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
