Cameron Braid wrote:
The "SELECT new DataClass(domainField1, domainField2) FROM class
DomainClass" is an excellent feature, though I propose the following
enhancements :
*a) Allow aliasing of the field names. *
this allows the the default constructor to be used, and the bean
properties set
The "SELECT new DataClass(domainField1, domainField2) FROM class
DomainClass" is an excellent feature, though I propose the following
enhancements :
a) Allow aliasing of the field names.
this allows the the default constructor to be used, and the bean
properties set by name.
SELECT new Dat
Hi, my next application will talk to two different databases, MS SqlServer
and Dbase. I know there is the linked-server function in MS SqlServer, with
which, I only need to talke with SQLServer and let it handle the transaction
with the Dbase table. I implemented it in SQLServer, but is it possible
Hi!
Look the code below:
A a = session.load(A.class, new Integer(1)); // ok
session.load(a, new Integer(10)); // throws an erros - 'object
already loaded in this session'
Is this a bug?? If the object 'a' on the second 'load()' call have an not
null ID it is reloaded ins
Hi,
We are in the process of bundling hibernate with Servoy platform
(www.servoy.com) to use hibernate as database depended layer for DDL
fired to backend databases and db depended SQL generation.
This works very well (hibernate is excellent lib!) but there are some
small issues we want to contri
My suggestion would be to have a different hibernate configuraiton for
your tests. I have a base test class that creates a mock setup of
instances in a fresh test database and then run the tests against that
before cleaning up.
There are dummy JNDI implementations around though if you'd prefer th
What you could do is have multiple setups so that some junit tests use the
container, others use it from a differnet location. You may be able to use
a container (Look at spring or the Avalon wrapper) to handle this. Just
configure two copys of Hibernate depending on where you need your
datasour