On 07/28/14 16:12, Alex Peshkoff wrote: > If we decide that having JDBC as a main firebird interface is a good > idea as a possible solution not (almost not) delaying FB3 release may be > used the following. Logically what FB3 interface does is very close to > JDBC. We can rename interfaces in Provider.h to make them match the > close-most JDBC interface (i.e. IAttachment becomes Connection, > IStatement => PreparedStatement, etc.) which will help build in next > version an interface which meets JDBC requirements at the same time > remaining compatible with what we have now.
Appears I was too hot saying this. FB3 provider interface is also that interface which is supported by all providers and routed over the wire. It does not seem useful to support all JDBC (including special datasets) in all providers. May be it's better to leave it as and have JDBC implemented side by side in yvalve, like currently ISC API. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
