Home » Modeling » EMF » [CDO] CDO server at Postgres: create table fails, table already exists
| [CDO] CDO server at Postgres: create table fails, table already exists [message #532178] |
Fri, 07 May 2010 12:17  |
Eclipse User |
|
|
|
Originally posted by: kuehnlenz.informatik.hu-berlin.de
Hi all,
I use the CDO server in combination with a Postgres RDBMS (see below for
the config file). Initially the used database contains no tables.
When I try to store my model, I get the following error message:
Thread-11 [debug.sql] CREATE TABLE eresource_CDOResourceFolder (cdo_id
BIGINT NOT NULL, cdo_version INTEGER NOT NULL, cdo_class BIGINT NOT
NULL, cdo_created BIGINT NOT NULL, cdo_revised BIGINT NOT NULL,
cdo_resource BIGINT NOT NULL, cdo_container BIGINT NOT NULL, cdo_feature
INTEGER NOT NULL, folder BIGINT, name text)
Thread-11 [debug.sql] -- ERROR: Relation »eresource_cdoresourcefolder«
already exists
What can I do or try?
Snippet from my cdo-server.xml config file:
<property name="overrideUUID" value="1ff5d226-b1f0-40fb-aba2-0c31b38c764f"/>
<property name="supportingAudits" value="true"/>
<property name="verifyingRevisions" value="false"/>
<property name="currentLRUCapacity" value="10000"/>
<property name="revisedLRUCapacity" value="100"/>
<store type="db">
<mappingStrategy type="horizontal">
<property name="qualifiedNames" value="true"/>
<property name="toManyReferences" value="ONE_TABLE_PER_REFERENCE"/>
<property name="toOneReferences" value="LIKE_ATTRIBUTES"/>
</mappingStrategy>
All the best,
Frank
|
|
|
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #532193 is a reply to message #532178] |
Fri, 07 May 2010 13:20  |
 Stefan Winkler
Messages: 307
Registered: July 2009
Location: Germany |
Senior Member |
|
|
Hi Frank,
Comments below.
Am 07.05.2010 14:17, schrieb Frank Kuehnlenz:
> Hi all,
>
> I use the CDO server in combination with a Postgres RDBMS (see below for
> the config file). Initially the used database contains no tables.
>
I have to admit that PostgreSQL ist the least tested DB with CDO. There
are also some tests in the testsuite which fail (only) for PostgreSQL
and I did not have time to investigate so far.
> When I try to store my model, I get the following error message:
>
> Thread-11 [debug.sql] CREATE TABLE eresource_CDOResourceFolder (cdo_id
> BIGINT NOT NULL, cdo_version INTEGER NOT NULL, cdo_class BIGINT NOT
> NULL, cdo_created BIGINT NOT NULL, cdo_revised BIGINT NOT NULL,
> cdo_resource BIGINT NOT NULL, cdo_container BIGINT NOT NULL, cdo_feature
> INTEGER NOT NULL, folder BIGINT, name text)
> Thread-11 [debug.sql] -- ERROR: Relation »eresource_cdoresourcefolder«
> already exists
>
> What can I do or try?
>
Just to be sure and eliminate some obvious things: Are you using the CVS
HEAD of CDO or some other version?
Can you check the log before that error: is there any model-related
table being created successfully before this one or is the failing
statement the first CREATE-Statement for a table (except the cdo_* tables)?
Can you exchange the PSQL for a H2 database temporarily and check if
that works?
Cheers
Stefan
|
|
|
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #532209 is a reply to message #532193] |
Fri, 07 May 2010 14:14 |
| Eclipse User |
|
|
|
Originally posted by: kuehnlenz.informatik.hu-berlin.de
Dear Stefan,
> I have to admit that PostgreSQL ist the least tested DB with CDO. There
> are also some tests in the testsuite which fail (only) for PostgreSQL
> and I did not have time to investigate so far.
In that case I assume, the MySQL support is better tested? What do you
suggest? H2, as mentioned for further investigation on that issue?
> Just to be sure and eliminate some obvious things: Are you using the CVS
> HEAD of CDO or some other version?
I use the R2_0_maintenance branch.
> Can you check the log before that error: is there any model-related
> table being created successfully before this one or is the failing
> statement the first CREATE-Statement for a table (except the cdo_* tables)?
The following tables were successfully created:
"eresource_cdoresourcefolder_nodes_list"
"eresource_cdoresource"
"eresource_cdoresourcefolder"
"eresource_cdoresource_contents_list"
"cdo_objects"
"cdo_package_units"
"cdo_package_infos"
"cdo_external_refs"
"cdo_repository"
> Can you exchange the PSQL for a H2 database temporarily and check if
> that works?
OK, I will do that and post the results.
Thanks for the first hints and all the best,
Frank
|
|
|
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #532484 is a reply to message #532209] |
Mon, 10 May 2010 08:52 |
Stefan Winkler
Messages: 307
Registered: July 2009
Location: Germany |
Senior Member |
|
|
Hi Frank,
comments below.
Am 07.05.2010 16:14, schrieb Frank Kuehnlenz:
>> I have to admit that PostgreSQL ist the least tested DB with CDO. There
>> are also some tests in the testsuite which fail (only) for PostgreSQL
>> and I did not have time to investigate so far.
>>
> In that case I assume, the MySQL support is better tested? What do you
> suggest? H2, as mentioned for further investigation on that issue?
>
Seems not too much like a DB-related problem to me. So, in general MySQL
should be tested better, but PSQL should also be fine (and this way we
get some more bug reports and more testing for that case.) So if you
have the flexibility, you can use PSQL and if an issue arises, check
with H2 if it works there.
>> Just to be sure and eliminate some obvious things: Are you using the CVS
>> HEAD of CDO or some other version?
>>
> I use the R2_0_maintenance branch.
>
I see. Again, if you are flexible enough, I recommend using HEAD (= the
3.0 version which will be delivered in Helios).
But your problem does still not sound like a known bug in 2.0.
>> Can you check the log before that error: is there any model-related
>> table being created successfully before this one or is the failing
>> statement the first CREATE-Statement for a table (except the cdo_* tables)?
>>
> The following tables were successfully created:
> "eresource_cdoresourcefolder_nodes_list"
> "eresource_cdoresource"
> "eresource_cdoresourcefolder"
> "eresource_cdoresource_contents_list"
> "cdo_objects"
> "cdo_package_units"
> "cdo_package_infos"
> "cdo_external_refs"
> "cdo_repository"
>
Mhh ... so the error message itself is indeed correct -
eresource_cdoresource does indeed exist already.
The problem seems to be that it is tried to be created twice.
Can you give some more information on your environment? Which model(s)
do you use?
How do you use them? From your original post, I figure, you are running
a CDOServer standaloine.
Can you post a snippet of your client code which shows how you establish
the connection and store your model?
Cheers,
Stefan
|
|
|
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #533585 is a reply to message #532484] |
Fri, 14 May 2010 15:54 |
| Eclipse User |
|
|
|
Originally posted by: kuehnlenz.informatik.hu-berlin.de
Hi Stefan!
Am 10.05.2010 10:54, schrieb Stefan Winkler:
> Seems not too much like a DB-related problem to me. So, in general MySQL
> should be tested better, but PSQL should also be fine (and this way we
> get some more bug reports and more testing for that case.) So if you
> have the flexibility, you can use PSQL and if an issue arises, check
> with H2 if it works there.
I see. If I use H2, than everything works fine. But with PostgreSQL I
still have problems.
> I see. Again, if you are flexible enough, I recommend using HEAD (= the
> 3.0 version which will be delivered in Helios).
> But your problem does still not sound like a known bug in 2.0.
OK. I switched to the HEAD. Now the problem is different, but still
exists using PostgreSQL database. The stand-alone CDO-server does not
even start any more. During start-up the following error occurs:
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_objects (cdo_id BIGINT, cdo_class BIGINT, cdo_created BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE UNIQUE
INDEX cdo_objects_idx0 ON cdo_objects (cdo_id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_branches (id INTEGER, name text, base_id INTEGER, base_time BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_branches_idx0 ON cdo_branches (id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_branches_idx1 ON cdo_branches (commit_time)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] -- ERROR:
Column »commit_time« does not exist. Trying to rollback operation
[ERROR] ERROR: Relation »cdo_branches« does not exist
org.eclipse.net4j.db.DBException: ERROR: Relation »cdo_branches« does
not exist
at org.eclipse.net4j.spi.db.DBAdapter.validateTable(DBAdapter.j ava:423)
at
org.eclipse.net4j.db.postgresql.PostgreSQLAdapter.createTabl e(PostgreSQLAdapter.java:164)
at org.eclipse.net4j.spi.db.DBAdapter.createTables(DBAdapter.ja va:109)
at org.eclipse.net4j.spi.db.DBSchema.create(DBSchema.java:106)
at
org.eclipse.emf.cdo.server.internal.db.DBStore.doActivate(DB Store.java:442)
at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
at
org.eclipse.emf.cdo.internal.server.Repository.doActivate(Re pository.java:1276)
at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
at
org.eclipse.emf.cdo.server.CDOServerUtil.addRepository(CDOSe rverUtil.java:128)
at
org.eclipse.emf.cdo.internal.server.RepositoryConfigurator.c onfigure(RepositoryConfigurator.java:93)
at
org.eclipse.emf.cdo.internal.server.bundle.CDOServerApplicat ion.doStart(CDOServerApplication.java:58)
at org.eclipse.net4j.util.om.OSGiApplication.start(OSGiApplicat ion.java:61)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at
org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(An yThreadAppLauncher.java:26)
at java.lang.Thread.run(Thread.java:619)
Just one table was successfully created:
"cdo_objects"
> Can you give some more information on your environment? Which model(s)
> do you use?
> How do you use them? From your original post, I figure, you are running
> a CDOServer standaloine.
Right, I use the CDOServer standalone.
I create my ecore-model out of an UML source (exported by MagicDraw) by
using the UML2 Extender SDK that integrates into the EMF Project
creation wizard.
After that I convert it to a CDO-native model.
> Can you post a snippet of your client code which shows how you establish
> the connection and store your model?
I use the editor generated out of the CDO-native ecore model.
I hope, this information helps to improve the PostgreSQL support.
All the best,
Frank
|
|
| |
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #534621 is a reply to message #534474] |
Wed, 19 May 2010 16:15 |
| Eclipse User |
|
|
|
Originally posted by: kuehnlenz.informatik.hu-berlin.de
Hi Stefan!
> I just fixed this in Bug 313486
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=313486).
> Please update and try again.
I followed the advice "You can update your development workspace with
re-importing the local.mpec as described above. Then the whole workspace
and the target platform are updated." but the file
'src/org/eclipse/emf/cdo/server/internal/db/CDODBSchema.java ' (that is
changed with the patch) was not updated to version 1.40, so I did it
manually for that single file.
I dropped all tables in the PostgresDB.
Now the following error occurs during start-up of the CDOserver:
[INFO] CDO server starting
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_objects (cdo_id BIGINT, cdo_class BIGINT, cdo_created BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE UNIQUE
INDEX cdo_objects_idx0 ON cdo_objects (cdo_id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_branches (id INTEGER, name text, base_id INTEGER, base_time BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_branches_idx0 ON cdo_branches (id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_package_units (id text, original_type INTEGER, time_stamp BIGINT,
package_data bytea)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_package_units_idx0 ON cdo_package_units (id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_package_infos (uri text, parent text, unit text, meta_lb BIGINT,
meta_ub BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_package_infos_idx0 ON cdo_package_infos (uri)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_package_infos_idx1 ON cdo_package_infos (parent)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_package_infos_idx2 ON cdo_package_infos (unit)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_external_refs (id BIGINT, uri text, committime BIGINT)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_external_refs_idx0 ON cdo_external_refs (id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_external_refs_idx1 ON cdo_external_refs (uri)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_commit_infos (commit_time BIGINT, branch_id INTEGER, user_id text,
comment text)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_commit_infos_idx0 ON cdo_commit_infos (commit_time)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_commit_infos_idx1 ON cdo_commit_infos (branch_id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
cdo_commit_infos_idx2 ON cdo_commit_infos (user_id)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
cdo_properties (name text, value LONG VARCHAR)
app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] -- Error:
Syntaxerror on »VARCHAR«. Trying to rollback operation
[ERROR] ERROR: Relation »cdo_properties« does not exist
org.eclipse.net4j.db.DBException: ERROR: Relation »cdo_properties« does
not exist
at org.eclipse.net4j.spi.db.DBAdapter.validateTable(DBAdapter.j ava:423)
at
org.eclipse.net4j.db.postgresql.PostgreSQLAdapter.createTabl e(PostgreSQLAdapter.java:164)
at org.eclipse.net4j.spi.db.DBAdapter.createTables(DBAdapter.ja va:109)
at org.eclipse.net4j.spi.db.DBSchema.create(DBSchema.java:106)
at
org.eclipse.emf.cdo.server.internal.db.DBStore.doActivate(DB Store.java:442)
at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
at
org.eclipse.emf.cdo.internal.server.Repository.doActivate(Re pository.java:1276)
at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
at
org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
at
org.eclipse.emf.cdo.server.CDOServerUtil.addRepository(CDOSe rverUtil.java:128)
at
org.eclipse.emf.cdo.internal.server.RepositoryConfigurator.c onfigure(RepositoryConfigurator.java:93)
at
org.eclipse.emf.cdo.internal.server.bundle.CDOServerApplicat ion.doStart(CDOServerApplication.java:58)
at org.eclipse.net4j.util.om.OSGiApplication.start(OSGiApplicat ion.java:61)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at
org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(An yThreadAppLauncher.java:26)
at java.lang.Thread.run(Thread.java:619)
In deed, just one table was created:
cdo_objects
(
cdo_id bigint,
cdo_class bigint,
cdo_created bigint
)
All the best,
Frank
|
|
|
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #534635 is a reply to message #534621] |
Wed, 19 May 2010 16:55 |
|
Am 19.05.2010 18:15, schrieb Frank Kuehnlenz:
> Hi Stefan!
>
>
>> I just fixed this in Bug 313486
>> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=313486).
>> Please update and try again.
>>
> I followed the advice "You can update your development workspace with
> re-importing the local.mpec as described above. Then the whole workspace
> and the target platform are updated." but the file
> 'src/org/eclipse/emf/cdo/server/internal/db/CDODBSchema.java ' (that is
> changed with the patch) was not updated to version 1.40, so I did it
> manually for that single file.
>
I also think that the Bucky re-import does not automatically CVS update
existing projects. We have to do it manually for all workspace projects ;-(
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> I dropped all tables in the PostgresDB.
> Now the following error occurs during start-up of the CDOserver:
>
> [INFO] CDO server starting
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_objects (cdo_id BIGINT, cdo_class BIGINT, cdo_created BIGINT)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE UNIQUE
> INDEX cdo_objects_idx0 ON cdo_objects (cdo_id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_branches (id INTEGER, name text, base_id INTEGER, base_time BIGINT)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_branches_idx0 ON cdo_branches (id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_package_units (id text, original_type INTEGER, time_stamp BIGINT,
> package_data bytea)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_package_units_idx0 ON cdo_package_units (id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_package_infos (uri text, parent text, unit text, meta_lb BIGINT,
> meta_ub BIGINT)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_package_infos_idx0 ON cdo_package_infos (uri)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_package_infos_idx1 ON cdo_package_infos (parent)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_package_infos_idx2 ON cdo_package_infos (unit)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_external_refs (id BIGINT, uri text, committime BIGINT)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_external_refs_idx0 ON cdo_external_refs (id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_external_refs_idx1 ON cdo_external_refs (uri)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_commit_infos (commit_time BIGINT, branch_id INTEGER, user_id text,
> comment text)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_commit_infos_idx0 ON cdo_commit_infos (commit_time)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_commit_infos_idx1 ON cdo_commit_infos (branch_id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE INDEX
> cdo_commit_infos_idx2 ON cdo_commit_infos (user_id)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] CREATE TABLE
> cdo_properties (name text, value LONG VARCHAR)
> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] -- Error:
> Syntaxerror on »VARCHAR«. Trying to rollback operation
> [ERROR] ERROR: Relation »cdo_properties« does not exist
> org.eclipse.net4j.db.DBException: ERROR: Relation »cdo_properties« does
> not exist
> at org.eclipse.net4j.spi.db.DBAdapter.validateTable(DBAdapter.j ava:423)
> at
> org.eclipse.net4j.db.postgresql.PostgreSQLAdapter.createTabl e(PostgreSQLAdapter.java:164)
> at org.eclipse.net4j.spi.db.DBAdapter.createTables(DBAdapter.ja va:109)
> at org.eclipse.net4j.spi.db.DBSchema.create(DBSchema.java:106)
> at
> org.eclipse.emf.cdo.server.internal.db.DBStore.doActivate(DB Store.java:442)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
> at
> org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
> at
> org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
> at
> org.eclipse.emf.cdo.internal.server.Repository.doActivate(Re pository.java:1276)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycl e.java:72)
> at
> org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:98)
> at
> org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(Life cycleUtil.java:88)
> at
> org.eclipse.emf.cdo.server.CDOServerUtil.addRepository(CDOSe rverUtil.java:128)
> at
> org.eclipse.emf.cdo.internal.server.RepositoryConfigurator.c onfigure(RepositoryConfigurator.java:93)
> at
> org.eclipse.emf.cdo.internal.server.bundle.CDOServerApplicat ion.doStart(CDOServerApplication.java:58)
> at org.eclipse.net4j.util.om.OSGiApplication.start(OSGiApplicat ion.java:61)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
> at
> org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(An yThreadAppLauncher.java:26)
> at java.lang.Thread.run(Thread.java:619)
>
>
> In deed, just one table was created:
> cdo_objects
> (
> cdo_id bigint,
> cdo_class bigint,
> cdo_created bigint
> )
>
> All the best,
> Frank
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
| |
| Re: [CDO] CDO server at Postgres: create table fails, table already exists [message #536943 is a reply to message #534855] |
Mon, 31 May 2010 14:34 |
| Eclipse User |
|
|
|
Originally posted by: kuehnlenz.informatik.hu-berlin.de
Hi Stefan,
thanks, it's fixed and working. :-)
All the best,
Frank
> Hi Frank,
>
> comments below.
>
>>> I just fixed this in Bug 313486
>>> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=313486).
>>> Please update and try again.
>>>
>> I followed the advice "You can update your development workspace with
>> re-importing the local.mpec as described above. Then the whole workspace
>> and the target platform are updated." but the file
>> 'src/org/eclipse/emf/cdo/server/internal/db/CDODBSchema.java ' (that is
>> changed with the patch) was not updated to version 1.40, so I did it
>> manually for that single file.
>>
>
> Ok, my fault. With "update" I meant CVS update. You don't have to do a
> Buckmister refresh usually - only if Eike changes something in the
> target platform.
> So, this time, please do a CVS update ;-)
>
>> I dropped all tables in the PostgresDB.
>> Now the following error occurs during start-up of the CDOserver:
>>
>>
> ...
>> app thread - org.eclipse.emf.cdo.server.app.0 [debug.sql] -- Error:
>> Syntaxerror on »VARCHAR«. Trying to rollback operation
>> [ERROR] ERROR: Relation »cdo_properties« does not exist
>> org.eclipse.net4j.db.DBException: ERROR: Relation »cdo_properties« does
>> not exist
>>
>>
> I have set up a psql database in a VMWare and did some quick testing
> with the CDO testsuite.
> I fixed that problem in http://bugs.eclipse.org/bugs/show_bug.cgi?id=313709
>
> After that, my repository came up just fine. So please (CVS-)update
> again and try again.
>
> Cheers,
> Stefan
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 14:50:19 GMT 2024
Powered by FUDForum. Page generated in 0.04018 seconds |
] 
Search
Help
Register
Login
Home
