Re: [enhydra] Postgres driver kills MySQL communication

["Sinisa Milosevic" <sinisa@xxxxxxxxxxxxx>]

Hi,

Objectid column name is a parameter in application conf file and you can set
for each application different value for objectid column.
I think that we should keep oid as a default objectid column name because of
compatibility. There is a possibility to override this value from
application conf file with one limit: values for objectid and version column
names must be the same in all applications (databases)

Regarding DODS and Enhydra separation. DODS is standalone and it can work
without Enhydra. But Enhydra 5.1.x can't work without dods-runtime.jar.
Enhydra creates DatabaseManager in StandardApplication class. Because of
that enhydra jars and dods-runtime.jar must be loaded by the same
classloader.

In Enhydra 6, DatabaseManager API is separated from EAF, and dods jars
(except databaseManageAPI ) are not needed for Enhydra application without
database connections.

Regards,
Sinisa


----- Original Message -----
From: "Petr Stehlik" <pstehlik@xxxxxxxxxx>
To: <enhydra@xxxxxxxxxxxxx>
Sent: Monday, November 01, 2004 4:45 PM
Subject: Re: [enhydra] Postgres driver kills MySQL communication


V Po, 25. 10. 2004 v 20:49, Sinisa Milosevic píše:
> Currently DODS reads configuration from file and sets static values for
oid
> and version columns in CoreDataStruct. So last configured application
> defines oid and version column names. If PostgreSQL database is the last
and
> it defines objectid as a oid column name, so your MySQL application
deosn't
> work.
> That's  an 'old Enhydra-DODS feature' (difference is that in earlier
version
> static fields was in CoreDO). Dirty solution will be using objectid as a
oid
> column name for MySQl applications. Also we will add this problem on our
> task list.

Sinisa,

If I understand it correctly then MySQL doesn't care what is the oid
column name while PostgreSql requires it named as "objectid". If there
is no other database that would have such requirement then I'd suggest
to simply modify the DODS to generate the oid column name as "objectid"
for all databases.

BTW, why do you call this solution a dirty one? Do you have a clearer
one in mind?

And last one: any idea why multiserver wrapper wants to load the
dods-runtime? Seems like DODS is not completely separated from rest of
Enhydra yet? (see the stack trace in previous mail).

Petr






----------------------------------------------------------------------------
----


>
> --
> You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx
mailing list.
> To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>