This isn't about a failed delete table statement. I had that error
too, but then I unchecked the drop boxes and that error went away.
From the text of the error I assumed it was coming from the set
transaction line, but I'm only guessing.
janine
On Aug 30, 2006, at 8:10 PM, Mike Schrag wrote:
> This is almost certainly because split on ;'s and execute each line
> independently. Anyone know how EOModeler-proper might do this and
> also have the ability to trap the failed delete table statements
> like it does?
>
> ms
>
> On Aug 30, 2006, at 9:20 PM, womai..ac.com wrote:
>
>> When I execute the SQL generated by Entity Modeler I get the
>> following error:
>>
>> java.sql.SQLException: Exception condition 384. Transaction MUST
>> be SERIALIZABLE, PESSIMISTIC. Do you want to cancel the rest of
>> the script?
>>
>> The first line of the generated SQL is
>>
>> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE, LOCKING PESSIMISTIC;
>>
>> I don't see any way to influence the SQL that's generated, and I
>> can't edit it. I have run it from FrontBase Manager and it
>> doesn't generate any errors there.
>>
>> So what can I do to fix this?
>>
>> thanks,
>>
>> janine
>>
>
This archive was generated by hypermail 2.0.0 : Wed Aug 30 2006 - 23:35:00 EDT