| [Teneo] Which PersistanceOptions suit a database also loaded from alternate source? [message #615429] |
Thu, 07 February 2008 14:37 |
 David Wynter
Messages: 4624
Registered: July 2009 |
Senior Member |
|
|
Hi,
This is a general question about which PersistanceOptions are best used
when you are generating a database that will be populated other than
through the Hibernate layer. More specifically which options add extra
columns used for sorting or similar (ordered list) where the column for
the sort id cannot be sourced when batch loading the database.
For example version property is useful for the object model but how then
do you populate these when bulk loading the database from say, files? I
also do not need a versioning system, my objects only need to be a
'point in time' record. So how do I prevent this being generated?
<version name="e_version"
access=" org.eclipse.emf.teneo.hibernate.mapping.property.VersionProp ertyHandler ">
<meta attribute="syntheticVersion">true</meta>
</version>
My preference is to make things less convenient for the object model and
more convenient for the bulk loading, at least to start. Overall I'd
like to minimise the number of tables generated. My current set of
PersistanceOptions are
props.setProperty(PersistenceOptions.MAXIMUM_SQL_NAME_LENGTH , "64");
props.setProperty(PersistenceOptions.JOIN_COLUMN_NAMING_STRA TEGY,
"simple");
props.setProperty(PersistenceOptions.ALSO_MAP_AS_CLASS, "false");
props.setProperty(PersistenceOptions.DEFAULT_TEMPORAL_VALUE, "DATE");
props.setProperty(PersistenceOptions.DISABLE_ECONTAINER_MAPP ING, "true");
Thx.
David
|
|
|
Powered by
FUDForum. Page generated in 0.01836 seconds
Search
Help
Register
Login
Home
