mhanney mrh5...@gmail.com writes:
regarding - All users of Oracle have a default schema that is
different than the schema where the tables live so all objects have to
be fully qualified with the schema name, you could use public
synonyms in Oracle:
CREATE OR REPLACE PUBLIC SYNONYM
Tyler Burd tb...@cudc.org writes:
Then you could have an NAnt target that would set up brail or some
other templating language, process the mapping files, and copy them
to a known directory.
Does that make sense?
Thank you very much, that makes perfectly sense. I already utilise
NAnt in
to set the connection.release_mode
property to on_close for this to work.
-Original Message-
From: nhusers@googlegroups.com [mailto:nhus...@googlegroups.com] On Behalf Of
Stefan Nobis
Sent: Wednesday, June 24, 2009 4:35 AM
To: nhusers@googlegroups.com
Subject: [nhusers] Re: Denormalized
...@googlegroups.com] On Behalf
Of Stefan Nobis
Sent: Wednesday, June 24, 2009 4:35 AM
To: nhusers@googlegroups.com
Subject: [nhusers] Re: Denormalized Domain Model
Tyler Burd tb...@cudc.org writes:
Then you could have an NAnt target that would set up brail or some
other templating language
Fabio Maulo fabioma...@gmail.com writes:
the default_schema/default_catalog, of each mapping or of the
session-factory-configuration does not work ?
It does not work for the SQL in the 'formula' attribute of a property
(at least it didn't seem to work in 2.0.1GA last time I tried this).
--
Ah ok... There shouldn't work because it is pure SQL and NH only touch it to
add the root alias and nothing more.
For All:
I would remember you that the mapping file has very few features regarding
multi-RDBMS SQLs support.
If I well remember there is only one place : database-object and
its
regarding - All users of Oracle have a default schema that is
different than the schema where the tables live so all objects have to
be fully qualified with the schema name, you could use public
synonyms in Oracle:
CREATE OR REPLACE PUBLIC SYNONYM TheTableName FOR
TheSchemaOwner.TheTableName;
Hmmm... you may have to push this into a build step that generates your mapping
files. So your formula would look something like this:
property name=MetaTrainName formula=(SELECT SomeField FROM
${Qualify('MyTableName')})/
Then you could have an NAnt target that would set up brail or some
