Deepak,
I had a problem with the plain 'ol vanila jdbc-odbc stuff, and went to
www.nogginware.com. They have a server which has a much better driver than
the other stuff. Once I started this server, registered my source in
windows...no problem. I about 100 mb of data queries and sql
commands....never had a problem.
Regards,
Lawrence
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Goel, Deepak
Sent: Wednesday, September 27, 2000 3:21 AM
To: Orion-Interest
Subject: FW: Primary Key problem
Hi Amir,
I'm interested in finding how were you able to make Orion work with
JDBC-ODBC layer. I was able to do it but I keep on getting error from the
ODBC driver "Connection is busy with results from the previous statement".
This I have seen to be a limitation of SQL Server driver, not of Orion or
any other software.
I'll appreciate if you can share your solution.
Thanks,
Deepak
-----Original Message-----
From: Amir Peivandi [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 25, 2000 1:26 PM
To: Orion-Interest
Subject: RE: Primary Key problem
Yes I did, bug #64
-----Original Message-----
From: Ernst de Haan [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 25, 2000 2:06 PM
To: Orion-Interest
Subject: Re: Primary Key problem
Hi Amir,
Have you added this to the Bugzilla bug database ? This way you will get the
attention of the Orion development team and you (and the rest of us) will be
able to track the status. :)
Ernst
Amir Peivandi wrote:
> Hi,
> I had a problem and it took me about five hours to find and fix it. I
though
> it could be useful for everybody to know and maybe it's a bug in Orion.
> When you have a CMP Entity bean which maps to a table with a certain
> condition as I explain here, the remove method fails with a message which
> says the object is being used and is locked by another active connection.
> This happens when you have a table with one, two or more fields and the
> primary key is a multi field key, consist of all the fields in the table.
It
> also happens when there is only one field in the table which is the
primary
> key. To resolve this issue you need to add at least a field to the table
> which is not part of the primary key!
>
> I'm using SQL server with ODBC/JDBC connection.
>
> Regards,
> Amir
>
>
