[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2658?page=c...
]
charbel commented on HHH-2658:
------------------------------
They are temporary during a client request, or during a specific treatement. After, the
entity definition with its table can be dropped.
It can be each time a new entityname using definitions of another created one. If we can
add new entity definition once the sessionfactory is created, then the pb is solved.
About synchronization, of course this kind of functionnality should only be used in only
some cases:
- We can add only new entities. The new entities shouldn't affect the existing ones
(example: new subclass...)
- We can't modify existing ones.
- Before removing entities, no other remaining ones should point to the one that we want
to delete.
And it is in charge of the developper to take care of synchronization between sessions
using temporary objects and removal of entities in sessionfactory.
Don't you think that we can have only simple cases of adding new entities to start
...
The ability to have new entities created at runtime.
----------------------------------------------------
Key: HHH-2658
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2658
Project: Hibernate3
Issue Type: New Feature
Reporter: charbel
Sometimes we would like to create a temporary table of a given entity, so it would be
great if we can add at runtime a new entity in the session factory, a copy of a given one
with just the tablename changed.
Example:
--------------
sessionfactory.addEntity(already_created_entity_name,table_parameters)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira