| Subject | Re: [Firebird-Java] Re: Native OO API |
|---|---|
| Author | Mark Rotteveel |
| Post date | 2018-11-04T12:43:27Z |
On 29-10-2018 15:41, vasiliy.yashkov@... [Firebird-Java] wrote:
change. I think that this should be a separate library entirely: both
the fboo bindings, and this batch API.
My main concern is that I don't think the proposed batch API (and
related interface/classes) belongs as part of the gds-ng API: it doesn't
mesh well with the JDBC part of the driver and it will need significant
changes to be usable from JDBC. It also deviates significantly from the
normal metadata usage (field descriptor, etc) in gds-ng.
My secondary concern is the additional burden of taking on the
maintenance of the OO API bindings as part of Jaybird. I hadn't realized
earlier the amount of code involved.
Mark
--
Mark Rotteveel
>As I also posted on GitHub, I'm not sure if I'm going to accept this
>
> Hi!
> I made PR of existing developments -
> https://github.com/FirebirdSQL/jaybird/pull/19.
> Waiting for feedback, suggestions.
change. I think that this should be a separate library entirely: both
the fboo bindings, and this batch API.
My main concern is that I don't think the proposed batch API (and
related interface/classes) belongs as part of the gds-ng API: it doesn't
mesh well with the JDBC part of the driver and it will need significant
changes to be usable from JDBC. It also deviates significantly from the
normal metadata usage (field descriptor, etc) in gds-ng.
My secondary concern is the additional burden of taking on the
maintenance of the OO API bindings as part of Jaybird. I hadn't realized
earlier the amount of code involved.
Mark
--
Mark Rotteveel