Subject | Re: SQLj |
---|---|
Author | Roman Rokytskyy |
Post date | 2003-09-18T23:41:38Z |
Ann,
here two separate issues:
- embedding Java Virtual Machine into Firebird (built-in or via JNI);
- allowing "opening" connections within stored procedures and UDFs.
From my point of view second issue is more challenging, since
connection "opened" inside stored procedure has to use the same
transaction as the connection through which stored procedure was
executed (in plain JDBC there's one-to-one relationship between
connection and transaction).
For JayBird it would be enough if SQLj layer provides GDS API +
tr_handle of the transaction in which SP is executed. In this case one
can create yet another GDS implementation like the one created by Ryan
Baldwin for type 2 and embedded Firebird.
Roman
> Any thoughts?I think we should move this discussion to Firebird-Architect. I see
here two separate issues:
- embedding Java Virtual Machine into Firebird (built-in or via JNI);
- allowing "opening" connections within stored procedures and UDFs.
From my point of view second issue is more challenging, since
connection "opened" inside stored procedure has to use the same
transaction as the connection through which stored procedure was
executed (in plain JDBC there's one-to-one relationship between
connection and transaction).
For JayBird it would be enough if SQLj layer provides GDS API +
tr_handle of the transaction in which SP is executed. In this case one
can create yet another GDS implementation like the one created by Ryan
Baldwin for type 2 and embedded Firebird.
Roman