Hi,
I've created that patch. The code in the ant task was all I could think
of...
A check for database fields would be quite nice actually, when working
on several machines, I sometimes forget to modify a table.
That could be done by doing a find on every perstisted class (load will
throw an error
classes => building the sessionFactory should do the job.
- Compile all named queries => OK except for SQL ones
- Validate the database schema by querying each table or something =>
Shouldn't be too hard with the "from A as a where 1=0"
Joris Verschoor wrote:
Hi,
I've create
o check a query. And if the db does not support something
similar, you can just ignore it. frequently used databases support it,
so i think it's nice to add it.
Joris Verschoor wrote:
compiling named queries only checks hql / mapping (sometimes hql is
correct, but the query it generates is n
Also Gavin's comments on "complete history" and "properly threaded"
messages is somewhat non-sense to me. Most e-mail programs properly
thread mailing lists. I don't have any problem with that and I don't
think people having difficulties with it. And if you want complete
history on a thread don't
Hi,
I was wondering weather it's a good idea to make a patch to cache the
generated classes by hibernate. This, to reduce startup time even more.
Let me know, if I should try to whip something up
Joris
---
SF email is sponsored by - The IT Prod
Gavin King wrote:
I think we made a big mistake by re-using the word “lazy” for
attribute-level lazy fetching. People think that will disable proxying.
Does anyone know another term we could use?
deferred?
---
SF email is sponsored by - The IT
Emmanuel Bernard wrote:
-1 esp the optional stuff in a separate zip
I do like having everything in 1 shot when I dl a lib.
Joris Verschoor wrote:
And what about the 3 directories in the current distro?
It's conveinient to just grab everything and copy it over to your own
li
Why not make 3 directories in the distribution?
Also, the hibernate3 dist. is 17MB!
I suggest splitting it up in 3 parts:
hibernate-src (zipped around 1.5mb)
hibernate-docs (zipped around 6.5mb)
hibernate-bin (zipped around 10mb)
I didn't move the build jars from the bin-dist to the src-dist, so I
Hello,
Personally I'm using the following pattern alot:
DomainObject o = Utils.getOne(session.find(xx));
When I expect to get exactly one from a query, or getOneorNone() if I
expect one or zero results.
I assume many people use something like that too, so I'd suggest
creating findOne() /
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/ger
10 matches
Mail list logo
