Subject | Re: Problems with type2 driver |
---|---|
Author | Roman Rokytskyy |
Post date | 2004-01-21T14:15:34Z |
Hi,
application directory structure and include current dir (".") in the
path. It should work.
heavy for small data transfers, embedded engine driver accesses file
directly from Java, there's no socket overhead at all.
Type 2 driver, with the IPC URL (server and port is not present)
should give your similar performance, but it will allow shared access
to the database (embedded engine locks the database for exclusive
use). Try to download jaybird.dll from SourceForge.net, maybe I sent
you an old version of it.
Best regards,
Roman Rokytskyy
> i got type 2 with embedded-server working now.I think you have to merge embedded server directory structure and your
> i need to put javaw.exe in the root directory of the
> embedded-server, this is working for testing purposes, but not for
> installations at our custumers.
application directory structure and include current dir (".") in the
path. It should work.
> Besides i'm really impressed by the perfomance of the type 2 driverThat's expected thing. Firebird's remote protocol seems to be too
> , it's nearly 100% faster for selects than type 4, even faster than
> interclient.
heavy for small data transfers, embedded engine driver accesses file
directly from Java, there's no socket overhead at all.
Type 2 driver, with the IPC URL (server and port is not present)
should give your similar performance, but it will allow shared access
to the database (embedded engine locks the database for exclusive
use). Try to download jaybird.dll from SourceForge.net, maybe I sent
you an old version of it.
Best regards,
Roman Rokytskyy