|
|
|
|
| Re: [CDO] mapping error with DB Store and StringToStringMap + List [message #426310 is a reply to message #426308] |
Tue, 23 December 2008 09:02   |
|
Kai, Vik,
I think your explanation is right.
Maybe Stefan wants to add something, but today is his birthday!
Live long and prosper for Stefan and the DBStore ;-)
Cheers
/Eike
----
http://thegordian.blogspot.com
Víctor Roldán Betancort schrieb:
> Hi Kai,
>
> in your model "tags" is defined as a multivalued EAttribute.
> Unfortunately, these aren't yet supported for DBStore. The core
> functionality to support it has been recently introduced in M4, but
> not the DBStore mapping implementation:
>
> 228190: Provide support for multivalued attributes
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=228190
>
> 254453: [DB] Support for multivalued attributes
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=254453
>
> Kai Schlamp escribió:
>> Hello.
>>
>> I have a strange mapping error (exceptions below) with the simple
>> test ecore model below.
>> The mapping results in a SQL Exception with Derby Store, when both
>> the StringToStringMap reference and the tags list attribute is in the
>> model.
>> When only one of both is present then the mapping works correctly.
>> I am not sure ... is this a bug or a incompatible ecore model?
>> I also attached a small sample project.
>>
>> Best regards,
>> Kai
>>
>> Ecore model:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <ecore:EPackage xmi:version="2.0"
>> xmlns:xmi="http://www.omg.org/XMI"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" name="cdo2model"
>> nsURI="http://cdo2.tester.org/cdo2model"
>> nsPrefix="org.cdo2.tester.model">
>> <eClassifiers xsi:type="ecore:EClass" name="DocumentStore">
>> <eStructuralFeatures xsi:type="ecore:EReference" name="documents"
>> upperBound="-1"
>> eType="#//Document" containment="true"/>
>> </eClassifiers>
>> <eClassifiers xsi:type="ecore:EClass" name="Document">
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
>> eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>> <eStructuralFeatures xsi:type="ecore:EReference"
>> name="propertiesM" upperBound="-1"
>> eType="#//StringToStringMap" containment="true"/>
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="tags"
>> upperBound="-1" eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>> </eClassifiers>
>> <eClassifiers xsi:type="ecore:EClass" name="StringToStringMap"
>> instanceClassName="java.util.Map$Entry">
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="key"
>> eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="value"
>> eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>> </eClassifiers>
>> </ecore:EPackage>
>>
>>
>> Exception:
>> [ERROR] SQL Exception: VALUES clause must contain at least one
>> element. Empty elements are not allowed.
>> org.eclipse.net4j.db.DBException: SQL Exception: VALUES clause must
>> contain at least one element. Empty elements are not allowed.
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:276)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.doInsertAttributes(StatementJDBCDelegate.java:93)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.AbstractJDBCDele gate.insertAttributes(AbstractJDBCDelegate.java:147)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeAtt ributes(ClassMapping.java:392)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeRev ision(ClassMapping.java:343)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.HorizontalClassMappin g.writeRevision(HorizontalClassMapping.java:47)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revision(DBStoreAccessor.java:518)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revisions(DBStoreAccessor.java:500)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.StoreAccessor.write(Stor eAccessor.java:151)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:367)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:281)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:328)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:204 )
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:146 )
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:146)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>>
>> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:317)
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:71)
>>
>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:237)
>> at org.eclipse.net4j.signal.Signal.run(Signal.java:145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn
>> Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> Source)
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: SQL Exception: VALUES clause must contain at least one
>> element. Empty elements are not allowed.
>> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unkno wn
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQL Exception(Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleExc eption(Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.EmbedConnection.handleException(U nknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.ConnectionChild.handleException(U nknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
>> at
>> org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unkn own Source)
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:272)
>>
>> ... 23 more
>> [ERROR] Rollback in DBStore: org.eclipse.net4j.db.DBException: SQL
>> Exception: VALUES clause must contain at least one element. Empty
>> elements are not allowed.
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:276)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.doInsertAttributes(StatementJDBCDelegate.java:93)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.AbstractJDBCDele gate.insertAttributes(AbstractJDBCDelegate.java:147)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeAtt ributes(ClassMapping.java:392)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeRev ision(ClassMapping.java:343)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.HorizontalClassMappin g.writeRevision(HorizontalClassMapping.java:47)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revision(DBStoreAccessor.java:518)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revisions(DBStoreAccessor.java:500)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.StoreAccessor.write(Stor eAccessor.java:151)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:367)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:281)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:328)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:204 )
>>
>> at
>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:146 )
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:146)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>>
>> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:317)
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:71)
>>
>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:237)
>> at org.eclipse.net4j.signal.Signal.run(Signal.java:145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn
>> Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> Source)
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: SQL Exception: VALUES clause must contain at least one
>> element. Empty elements are not allowed.
>> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unkno wn
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQL Exception(Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleExc eption(Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.EmbedConnection.handleException(U nknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.ConnectionChild.handleException(U nknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
>> at
>> org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unkn own Source)
>> at
>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:272)
>>
>> ... 23 more
>>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
|
| Re: [CDO] mapping error with DB Store and StringToStringMap + List [message #426334 is a reply to message #426320] |
Wed, 24 December 2008 13:51 |
 Kai Schlamp
Messages: 344
Registered: July 2009 |
Senior Member |
|
|
Yep, it denpends only on the "tags" attribute.
Is is fully independent of the StringToStringMap I found out afterwards.
So it is endeed the mentioned "bug".
Best regards,
Kai
Simon McDuff schrieb:
> Forgot was I just said... the problem isn't about StringToStringMap but
> about
> <eClassifiers xsi:type="ecore:EClass" name="Document">
> > <eStructuralFeatures xsi:type="ecore:EAttribute" name="tags"
> > ordered="false" unique="false"
> > upperBound="-1" eType="ecore:EDataType
> > http://www.eclipse.org/emf/2002/Ecore#//EString"
> > defaultValueLiteral="nothing"/>
>
> Sorry!! Yes it could be related to multivalued attribute bug that VIk
> mentionned.
>
> Simon
>
> Simon McDuff wrote:
>> humm.. I'm not sure about that. A Map of StringToStringMap is in fact
>> a list of a structure that have two String. I don't see any
>> multi-valued list in there..
>>
>> class StringToString
>> String key;
>> String value;
>>
>> Khai said it was working in the previous version.. does it mean he
>> didn't have any error... or it was working... ?
>>
>> Simon
>>
>> Eike Stepper wrote:
>>> Kai, Vik,
>>>
>>> I think your explanation is right.
>>> Maybe Stefan wants to add something, but today is his birthday!
>>> Live long and prosper for Stefan and the DBStore ;-)
>>>
>>> Cheers
>>> /Eike
>>>
>>> ----
>>> http://thegordian.blogspot.com
>>>
>>>
>>>
>>> Víctor Roldán Betancort schrieb:
>>>> Hi Kai,
>>>>
>>>> in your model "tags" is defined as a multivalued EAttribute.
>>>> Unfortunately, these aren't yet supported for DBStore. The core
>>>> functionality to support it has been recently introduced in M4, but
>>>> not the DBStore mapping implementation:
>>>>
>>>> 228190: Provide support for multivalued attributes
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=228190
>>>>
>>>> 254453: [DB] Support for multivalued attributes
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=254453
>>>>
>>>> Kai Schlamp escribió:
>>>>> Hello.
>>>>>
>>>>> I have a strange mapping error (exceptions below) with the simple
>>>>> test ecore model below.
>>>>> The mapping results in a SQL Exception with Derby Store, when both
>>>>> the StringToStringMap reference and the tags list attribute is in
>>>>> the model.
>>>>> When only one of both is present then the mapping works correctly.
>>>>> I am not sure ... is this a bug or a incompatible ecore model?
>>>>> I also attached a small sample project.
>>>>>
>>>>> Best regards,
>>>>> Kai
>>>>>
>>>>> Ecore model:
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <ecore:EPackage xmi:version="2.0"
>>>>> xmlns:xmi="http://www.omg.org/XMI"
>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>> xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
>>>>> name="cdo2model"
>>>>> nsURI="http://cdo2.tester.org/cdo2model"
>>>>> nsPrefix="org.cdo2.tester.model">
>>>>> <eClassifiers xsi:type="ecore:EClass" name="DocumentStore">
>>>>> <eStructuralFeatures xsi:type="ecore:EReference"
>>>>> name="documents" upperBound="-1"
>>>>> eType="#//Document" containment="true"/>
>>>>> </eClassifiers>
>>>>> <eClassifiers xsi:type="ecore:EClass" name="Document">
>>>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
>>>>> eType="ecore:EDataType
>>>>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>>>>> <eStructuralFeatures xsi:type="ecore:EReference"
>>>>> name="propertiesM" upperBound="-1"
>>>>> eType="#//StringToStringMap" containment="true"/>
>>>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="tags"
>>>>> upperBound="-1" eType="ecore:EDataType
>>>>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>>>>> </eClassifiers>
>>>>> <eClassifiers xsi:type="ecore:EClass" name="StringToStringMap"
>>>>> instanceClassName="java.util.Map$Entry">
>>>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="key"
>>>>> eType="ecore:EDataType
>>>>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>>>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="value"
>>>>> eType="ecore:EDataType
>>>>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>>>>> </eClassifiers>
>>>>> </ecore:EPackage>
>>>>>
>>>>>
>>>>> Exception:
>>>>> [ERROR] SQL Exception: VALUES clause must contain at least one
>>>>> element. Empty elements are not allowed.
>>>>> org.eclipse.net4j.db.DBException: SQL Exception: VALUES clause must
>>>>> contain at least one element. Empty elements are not allowed.
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:276)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.doInsertAttributes(StatementJDBCDelegate.java:93)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.AbstractJDBCDele gate.insertAttributes(AbstractJDBCDelegate.java:147)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeAtt ributes(ClassMapping.java:392)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeRev ision(ClassMapping.java:343)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.HorizontalClassMappin g.writeRevision(HorizontalClassMapping.java:47)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revision(DBStoreAccessor.java:518)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revisions(DBStoreAccessor.java:500)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.StoreAccessor.write(Stor eAccessor.java:151)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:367)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:281)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:328)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:204 )
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:146 )
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:146)
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>>>>>
>>>>> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:317)
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:71)
>>>>>
>>>>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:237)
>>>>> at org.eclipse.net4j.signal.Signal.run(Signal.java:145)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>>>> Source)
>>>>> at java.lang.Thread.run(Unknown Source)
>>>>> Caused by: SQL Exception: VALUES clause must contain at least one
>>>>> element. Empty elements are not allowed.
>>>>> at
>>>>> org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unkno wn Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQL Exception(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleExc eption(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.EmbedConnection.handleException(U nknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.ConnectionChild.handleException(U nknown
>>>>> Source)
>>>>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unkn own
>>>>> Source)
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:272)
>>>>>
>>>>> ... 23 more
>>>>> [ERROR] Rollback in DBStore: org.eclipse.net4j.db.DBException: SQL
>>>>> Exception: VALUES clause must contain at least one element. Empty
>>>>> elements are not allowed.
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:276)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.doInsertAttributes(StatementJDBCDelegate.java:93)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.AbstractJDBCDele gate.insertAttributes(AbstractJDBCDelegate.java:147)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeAtt ributes(ClassMapping.java:392)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.ClassMapping.writeRev ision(ClassMapping.java:343)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.HorizontalClassMappin g.writeRevision(HorizontalClassMapping.java:47)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revision(DBStoreAccessor.java:518)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write Revisions(DBStoreAccessor.java:500)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.StoreAccessor.write(Stor eAccessor.java:151)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.DBStoreAccessor.write (DBStoreAccessor.java:367)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext Impl.write(TransactionCommitContextImpl.java:281)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicatingCommit(CommitTransactionIndication.ja va:328)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:204 )
>>>>>
>>>>> at
>>>>> org.eclipse.emf.cdo.internal.server.protocol.CommitTransacti onIndication.indicating(CommitTransactionIndication.java:146 )
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithMonitoring.indicating (IndicationWithMonitoring.java:146)
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedIn put(IndicationWithResponse.java:90)
>>>>>
>>>>> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:317)
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:63)
>>>>>
>>>>> at
>>>>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:71)
>>>>>
>>>>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:237)
>>>>> at org.eclipse.net4j.signal.Signal.run(Signal.java:145)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>>>> Source)
>>>>> at java.lang.Thread.run(Unknown Source)
>>>>> Caused by: SQL Exception: VALUES clause must contain at least one
>>>>> element. Empty elements are not allowed.
>>>>> at
>>>>> org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unkno wn Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQL Exception(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleExc eption(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.EmbedConnection.handleException(U nknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.ConnectionChild.handleException(U nknown
>>>>> Source)
>>>>> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unkn own
>>>>> Source)
>>>>> at
>>>>> org.eclipse.emf.cdo.server.internal.db.jdbc.StatementJDBCDel egate.sqlUpdate(StatementJDBCDelegate.java:272)
>>>>>
>>>>> ... 23 more
>>>>>
|
|
|
Powered by
FUDForum. Page generated in 0.04465 seconds
] 
Search
Help
Register
Login
Home
