Quantcast

Ignore Explicit COMMIT/ROLLBACK?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Ignore Explicit COMMIT/ROLLBACK?

Michael Lynch

Can LucidDB be configured to ignore COMMIT and ROLLBACK statements?

I am trying connect to a LucidDB instance from a third party Business Intelligence tool.  It appears that their software is sending explicit COMMIT and ROLLBACK statements when it is retrieving metadata.


Michael Lynch
Software Architect
Integrated Services, Inc.
[hidden email]
www.ints.com
P:503-968-8100
F:503-968-9100

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

ngoodman
On Sep 3, 2010, at 1:13 PM, Michael Lynch wrote:

> Can LucidDB be configured to ignore COMMIT and ROLLBACK statements?
>
> I am trying connect to a LucidDB instance from a third party Business Intelligence tool.  It appears that their software is sending explicit COMMIT and ROLLBACK statements when it is retrieving metadata.

This has been done in the PG2LucidDB project (ie, the ability to talk "postgres" to a LucidDB instance) but we haven't done anything similar on the core server.  It's a good feature and a general purpose query rewriting capability (so we can address exactly these types of needs) was discussed this week during side conversations at the Eigenbase meetup.

Let me look around and see what I can come up with... Which tool are you attempting to connect, btw?

Nick
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

Michael Lynch

Thank you so much for your response!  I am excited by my initial experiments with LucidDB and would very much like to use it with the our BI Tool.  The tool we are using is INetSoft Style Intelligence (http://www.inetsoft.com/.)

Thanks again,

- Michael

Michael Lynch
Software Architect
Integrated Services, Inc.
[hidden email]
www.ints.com
P:503-968-8100
F:503-968-9100


On Fri, Sep 3, 2010 at 4:33 PM, Nicholas Goodman <[hidden email]> wrote:
On Sep 3, 2010, at 1:13 PM, Michael Lynch wrote:

> Can LucidDB be configured to ignore COMMIT and ROLLBACK statements?
>
> I am trying connect to a LucidDB instance from a third party Business Intelligence tool.  It appears that their software is sending explicit COMMIT and ROLLBACK statements when it is retrieving metadata.

This has been done in the PG2LucidDB project (ie, the ability to talk "postgres" to a LucidDB instance) but we haven't done anything similar on the core server.  It's a good feature and a general purpose query rewriting capability (so we can address exactly these types of needs) was discussed this week during side conversations at the Eigenbase meetup.

Let me look around and see what I can come up with... Which tool are you attempting to connect, btw?

Nick
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

John Sichi
Administrator
Michael Lynch wrote:
>
> Thank you so much for your response!  I am excited by my initial
> experiments with LucidDB and would very much like to use it with the our
> BI Tool.  The tool we are using is INetSoft Style Intelligence
> (http://www.inetsoft.com/.)

It would be a good idea to log a bug report with them as well, since
it's a JDBC application error to attempt COMMIT/ROLLBACK on an
autocommit connection.

JVS

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

Michael Lynch

Already done, although at this point it stands as a feature request instead of a defect.

Their initial response was to say that it was the driver's fault for not supporting COMMIT/ROLLBACK.  This seemed like a typical tech support response (to blame someone else), but I am not familiar enough with the JDBC "spec" to argue the point (and it may not matter much in the end.)

I did briefly look though the JDBC connection properties in SQuirrel and didn't see anything that explicitly referred to autocommit.   How should they determine that it is an autocommit connection?

Thanks again,

Michael Lynch
Software Architect
Integrated Services, Inc.
[hidden email]
www.ints.com
P:503-968-8100
F:503-968-9100


On Fri, Sep 3, 2010 at 10:42 PM, John V. Sichi <[hidden email]> wrote:
Michael Lynch wrote:
>
> Thank you so much for your response!  I am excited by my initial
> experiments with LucidDB and would very much like to use it with the our
> BI Tool.  The tool we are using is INetSoft Style Intelligence
> (http://www.inetsoft.com/.)

It would be a good idea to log a bug report with them as well, since
it's a JDBC application error to attempt COMMIT/ROLLBACK on an
autocommit connection.

JVS

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

John Sichi
Administrator
Michael Lynch wrote:

>
> Already done, although at this point it stands as a feature request
> instead of a defect.
>
> Their initial response was to say that it was the driver's fault for not
> supporting COMMIT/ROLLBACK.  This seemed like a typical tech support
> response (to blame someone else), but I am not familiar enough with the
> JDBC "spec" to argue the point (and it may not matter much in the end.)
>
> I did briefly look though the JDBC connection properties in SQuirrel and
> didn't see anything that explicitly referred to autocommit.   How should
> they determine that it is an autocommit connection?

See the snippets below from

http://download.oracle.com/javase/6/docs/api/java/sql/Connection.html

They make it clear that a JDBC driver should throw an exception if
commit() is called on an autocommit connection, and autocommit is the
default.  LucidDB doesn't support user-level transactions, so its
driver's setAutoCommit method also throws an exception if the
application requests manual commit mode.

It's not explicitly defined whether executing the SQL language COMMIT
statement should yield the same behavior as calling the commit() API
method, but common sense certainly dictates it should.

JVS

----

"By default a Connection object is in auto-commit mode"

boolean getAutoCommit()
           Retrieves the current auto-commit mode for this Connection
object.

----

void commit()
             throws SQLException

     Makes all changes made since the previous commit/rollback permanent
and releases any database locks currently held by this Connection
object. This method should be used only when auto-commit mode has been
disabled.

Throws:
     SQLException - if a database access error occurs, this method is
called while participating in a distributed transaction, if this method
is called on a closed conection or this Connection object is in
auto-commit mode

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Ignore Explicit COMMIT/ROLLBACK?

Michael Lynch
In reply to this post by ngoodman

I wrote a little wrapper around the LucidDB JDBC driver to do some primitive query re-writing as you described.  It turns out that the tool (INetSoft StyleIntelligence) is not sending explicit COMMITS or ROLLBACKS, rather they are calling commit() and rollback() on the connection (and in some cases calling setAutoCommit(false)) - all of which cause the same exception.

The good news is that I am now able to connect to a LucidDB instance using the reporting tool.

Thanks again!

- Michael

On Fri, Sep 3, 2010 at 4:33 PM, Nicholas Goodman <[hidden email]> wrote:
On Sep 3, 2010, at 1:13 PM, Michael Lynch wrote:

> Can LucidDB be configured to ignore COMMIT and ROLLBACK statements?
>
> I am trying connect to a LucidDB instance from a third party Business Intelligence tool.  It appears that their software is sending explicit COMMIT and ROLLBACK statements when it is retrieving metadata.

This has been done in the PG2LucidDB project (ie, the ability to talk "postgres" to a LucidDB instance) but we haven't done anything similar on the core server.  It's a good feature and a general purpose query rewriting capability (so we can address exactly these types of needs) was discussed this week during side conversations at the Eigenbase meetup.

Let me look around and see what I can come up with... Which tool are you attempting to connect, btw?

Nick
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
Loading...