hibernate-devel — development

[Hibernate] [PATCH] Quoted SQL identifiers

[Jean-Francois n. <jfn...@pr...>]

Hi.

I sent a patch via SourceForge to support quoted SQL identifiers.

See:
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D428710&aid=3D630661=
&grou
p_id=3D40712

Thanks.

Jean-Francois

Re: [Hibernate] Why this line...

[Max R. A. <ma...@eo...>]

Ok.

As described shortly in my last email concerning this matter I had a
configuraiton
where the Class could not be found neither via the lookup or by comparing
isAssignable - even
though it was a Class with the same name.

The problem was that it was loaded by another classloader (this can happen
when lurking around
with J2EE and servlet containers) and then the query would never get any
results and return null!

Maybe we could add a check before the result is returned wether it is null
or not - and then throw
an IllegalStateException or similar - warning that something truly bizar is
happening ?

/max

----- Original Message -----
From: "Gavin King" <ga...@ap...>
To: "Max Rydahl Andersen" <ma...@eo...>;
<hib...@li...>
Sent: Tuesday, October 29, 2002 6:22 PM
Subject: Re: [Hibernate] Why this line...


> This is part of a preprocessing phase where we scan the query for Java
> classes that *aren't* mapped in the mapping document and turn the single
> query into n queries against the n implementors of that interface. So that
> method says: if the passed token is the class name of an unmapped class,
> return the names of all the implementors of that class. Otherwise return
> null, and ignore the token.
>
>
> ----- Original Message -----
> From: "Max Rydahl Andersen" <ma...@eo...>
> To: <hib...@li...>
> Sent: Tuesday, October 29, 2002 3:16 AM
> Subject: [Hibernate] Why this line...
>
>
> > In SessionFactoryImpl I found this code:
> >
> > public String[] getImplementors(Class clazz) {
> >
> > if ( classPersisters.containsKey(clazz) ) return null;
> >
> > ...
> >
> > ..
> >
> > }
> >
> >
> >
> > Why should getImplementors return null if clazz is inside the
> > classPersisters ?
> >
> >
> >
> > /max
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > hibernate-devel mailing list
> > hib...@li...
> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

[Hibernate] cvs mail notifications

[Max R. A. <ma...@eo...>]

Hi!

Im in the process of making sf.net's cvs server send us notifications on the
hibernate-commits list when
someone commits to the list.

Just one problem, I've followed the instructions on
http://sourceforge.net/docman/display_doc.php?docid=772&group_id=1#support
very carefully, but for some reason whenever you are doing a cvs commit you
will get the folloowing error message:
"sh: /cvsroot/hibernate/CVSROOT/syncmail: No such file or directory"

But don't worry -- your commit will truly commit, it is just syncmail
complaining over something.
I've sent a support-request to sf.net concerning the matter - and I'll
inform you when something happens (either good or bad :)

Sorry - for the inconvenience!

/max

Re: [Hibernate] Why this line...

[Gavin K. <ga...@ap...>]

This is part of a preprocessing phase where we scan the query for Java
classes that *aren't* mapped in the mapping document and turn the single
query into n queries against the n implementors of that interface. So that
method says: if the passed token is the class name of an unmapped class,
return the names of all the implementors of that class. Otherwise return
null, and ignore the token.


----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Tuesday, October 29, 2002 3:16 AM
Subject: [Hibernate] Why this line...


> In SessionFactoryImpl I found this code:
>
> public String[] getImplementors(Class clazz) {
>
> if ( classPersisters.containsKey(clazz) ) return null;
>
> ...
>
> ..
>
> }
>
>
>
> Why should getImplementors return null if clazz is inside the
> classPersisters ?
>
>
>
> /max
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Re: [Hibernate] Changelog correction :)

[Gavin K. <ga...@ap...>]

Sorry!

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Wednesday, October 30, 2002 2:42 AM
Subject: [Hibernate] Changelog correction :)


> Hi!
>
> Just to be nitty-gritty...
>
> My name is: Max Andersen, not Max Anderson as it is stated in the
changelog.
>
> Anderson is a Swedish/Norwegian name, and Andersen is a Danish name - and
> i'm a Dane :)
>
> /max
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

[Hibernate] Changelog correction :)

[Max R. A. <ma...@eo...>]

Hi!

Just to be nitty-gritty...

My name is: Max Andersen, not Max Anderson as it is stated in the changelog.

Anderson is a Swedish/Norwegian name, and Andersen is a Danish name - and
i'm a Dane :)

/max

RE: [Hibernate] semantic of log WARN

[Brad C. <bra...@wo...>]

i agree, my preference is that these messages should be info, not warn.  =
however, hibernate internally uses jakarta commons-logging, so i don't =
quite know how the logging level is controlled with that.  i won't have =
a chance to look at it for a couple days.

brad

> -----Original Message-----
> From: Joseph Panico [mailto:joe...@ho...]
> Sent: Tuesday, 29 October 2002 3:28 AM
> To: hib...@li...
> Subject: [Hibernate] semantic of log WARN
>=20
>=20
> Hello,
>=20
> (I'm using hibernate-1.1)
>=20
> I'm integrating a lot of different frameworks that all use=20
> log4j as their=20
> logging mechanism. In all of the other frameworks, WARN level=20
> messages are=20
> reserved for "pathological conditions". They indicate that=20
> something is=20
> seriously out of whack, but perhaps not seriously enough to warrant=20
> terminating the program (ERROR). Unfortunately, hibernate=20
> seems to take a=20
> much more liberal view of WARN. For instance, I see this:
>=20
> 12:25:15,787 (SocketListener-2) [WARN:hibernate.Environment --=20
> hibernate.properties not found]
> 12:25:20,854 (SocketListener-2)=20
> [WARN:impl.SessionFactoryObjectFactory -- no=20
> JDNI name configured]
>=20
> These are not pathological conditions, and it seems to me=20
> that INFO would be=20
> more appropriate in this setting.
>=20
> Am I the only one who feels this way? What is the semantic of=20
> a Hibernate=20
> warning (as opposed to INFO and ERROR)?
>=20
> Joseph Panico
> joe...@ho...
>=20
>=20
>=20
> _________________________________________________________________
> Internet access plans that fit your lifestyle -- join MSN.=20
> http://resourcecenter.msn.com/access/plans/default.asp
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>=20

[Hibernate] semantic of log WARN

[Joseph P. <joe...@ho...>]

Hello,

(I'm using hibernate-1.1)

I'm integrating a lot of different frameworks that all use log4j as their 
logging mechanism. In all of the other frameworks, WARN level messages are 
reserved for "pathological conditions". They indicate that something is 
seriously out of whack, but perhaps not seriously enough to warrant 
terminating the program (ERROR). Unfortunately, hibernate seems to take a 
much more liberal view of WARN. For instance, I see this:

12:25:15,787 (SocketListener-2) [WARN:hibernate.Environment -- 
hibernate.properties not found]
12:25:20,854 (SocketListener-2) [WARN:impl.SessionFactoryObjectFactory -- no 
JDNI name configured]

These are not pathological conditions, and it seems to me that INFO would be 
more appropriate in this setting.

Am I the only one who feels this way? What is the semantic of a Hibernate 
warning (as opposed to INFO and ERROR)?

Joseph Panico
joe...@ho...



_________________________________________________________________
Internet access plans that fit your lifestyle -- join MSN. 
http://resourcecenter.msn.com/access/plans/default.asp

Re: [Hibernate] Why this line...

[Max R. A. <ma...@eo...>]

Just a side note:

I discovered the line while pondering on another very weird and seldom
situation: That hibernate had been configured with domain classes that is
not assignable with the classes found when executing queries. This can occur
in J2EE applications where you in certain situations are required to add
your own util jars and other jars to the app-servers own classpath.

What happens is that the check for assignability in getImplementors actually
can fail even though the class'es names are exactly the same - but because
the classloaders are different it will return false. This again results in
the session.find method returning null as an result, because it could not
genereate a valid query!

I have the "insane" usecase at my machine, but it is hardly reproducible,
but I'll try to make a small patch that will inform me if something is
really goooey :) (I should be able to do it by checking wether the class'es
names are equal bot not assignable - then we got a problem, maybe issue a
warning ?)

/max

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Monday, October 28, 2002 5:16 PM
Subject: [Hibernate] Why this line...


> In SessionFactoryImpl I found this code:
>
> public String[] getImplementors(Class clazz) {
>
> if ( classPersisters.containsKey(clazz) ) return null;
>
> ...
>
> ..
>
> }
>
>
>
> Why should getImplementors return null if clazz is inside the
> classPersisters ?
>
>
>
> /max
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

[Hibernate] Why this line...

[Max R. A. <ma...@eo...>]

In SessionFactoryImpl I found this code:

public String[] getImplementors(Class clazz) {

if ( classPersisters.containsKey(clazz) ) return null;

...

..

}



Why should getImplementors return null if clazz is inside the
classPersisters ?



/max

Re: [Hibernate] Metadata, codegenerator et.al...

[Gavin K. <ga...@ap...>]

Unfortunately, the parsing code sucks. It sucks because

(a) it was written to "do the job", not be elegant
(b) it uses DOM
(c) there are a lot of places where things are implied by a combination of
the mapping file and the class itself

We could fix (b) by chucking the whole .map package and re-doing it using
some databinding fwk. I'm not sure whats the best for databinding currently
though. I would actually very much like to do this, to get rid of ugly code.
However, currently the design of the map package has not been a problem for
_me_ in the functionality I've been concentrating upon.

(c) is more difficult since it means that plenty of perfectly legitimate
mapping files can't be fully compiled without the classes. However, if we
chucked + re-did with databinding, we would need a second-pass to fill in
reflected values *anyway*, so maybe there is also a way forward there.

Now, if it turns out to be worthwhile doing this, there is one thing working
in our favor. We have heaps of unit tests, so we shouldn't need to be
worried about breaking things.

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: "Gavin King" <ga...@ap...>
Sent: Monday, October 28, 2002 1:33 AM
Subject: Re: [Hibernate] Metadata, codegenerator et.al...


> > > Any suggestions on formats/semantics of it all ? (property and
attribute
> > are
> > > dubious names in
> > > this db context, so is custom-attribute a good tag-name/metadata name
> for
> > > it ?)
> >
> > How about <metadata name="foo" value="bar"/>
>
> So, we got a metadata to augment/describe the metadata - well, I suppose
> that's the
> way it is supposed to be :)
>
> > > I would love to contribute the above mentioned stuff, if I had a clear
> > > vision on the existing parsing and building
> > > of metadata info in Hibernate....and currently it seems that Hibernate
> > > CANNOT parse an hbm.xml without
> > > having the related classes in its classpath ...and that is somewhat of
> an
> > > limitiation when it is a codegenerator that
> > > is about to generate these classes :)
> >
> > Good point.
> >
> > > Anyone with a clear vision and understanding of hibernates hbm.xml
> parsing
> > > that can untangle that web of assumptions
> > > in the hibernate core ?
> >
> > Okay, there are two levels of metadata. The "parsed" metadata,
represented
> > by the cirrus.hibernate.map package and the "compiled" metadata which is
> > really just the internal state of the EntityPersisters.
> >
> > You have no chance of using the compiled metadata. On the other hand, it
> > would be reasonably easy to remove any references to actual classes from
> the
> > cirrus.hibernate.map package which is used to represent the internal
state
> > of Datastore. If you could clean up that package a little bit, it would
> > probably do what you want. Now, that package is definately not meant to
be
> > exposed to users, but you might be able to expose it to the toolset.
>
> I've tried to dig into the map package, but it seems there is waaay to
many
> places
> the code tries to do a classForName to check if it can continue to do its
> parsing -
> and by waaay to many, I mean waaay to many for me to go changing the parse
> semantics :(
>
> So, I'll try to "just" add the metadata tag stuff...that should be doable
> without changing much
> of the semantics, but it sure won't be as usable when the parser still
> requires the classes to
> be available ;(
>
> /max

Fw: [Hibernate] Metadata, codegenerator et.al...

[Max R. A. <ma...@eo...>]

forgot to send it to the list instead of directly ....so here you go :)

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: "Gavin King" <ga...@ap...>
Sent: Sunday, October 27, 2002 3:33 PM
Subject: Re: [Hibernate] Metadata, codegenerator et.al...


> > > Any suggestions on formats/semantics of it all ? (property and
attribute
> > are
> > > dubious names in
> > > this db context, so is custom-attribute a good tag-name/metadata name
> for
> > > it ?)
> >
> > How about <metadata name="foo" value="bar"/>
>
> So, we got a metadata to augment/describe the metadata - well, I suppose
> that's the
> way it is supposed to be :)
>
> > > I would love to contribute the above mentioned stuff, if I had a clear
> > > vision on the existing parsing and building
> > > of metadata info in Hibernate....and currently it seems that Hibernate
> > > CANNOT parse an hbm.xml without
> > > having the related classes in its classpath ...and that is somewhat of
> an
> > > limitiation when it is a codegenerator that
> > > is about to generate these classes :)
> >
> > Good point.
> >
> > > Anyone with a clear vision and understanding of hibernates hbm.xml
> parsing
> > > that can untangle that web of assumptions
> > > in the hibernate core ?
> >
> > Okay, there are two levels of metadata. The "parsed" metadata,
represented
> > by the cirrus.hibernate.map package and the "compiled" metadata which is
> > really just the internal state of the EntityPersisters.
> >
> > You have no chance of using the compiled metadata. On the other hand, it
> > would be reasonably easy to remove any references to actual classes from
> the
> > cirrus.hibernate.map package which is used to represent the internal
state
> > of Datastore. If you could clean up that package a little bit, it would
> > probably do what you want. Now, that package is definately not meant to
be
> > exposed to users, but you might be able to expose it to the toolset.
>
> I've tried to dig into the map package, but it seems there is waaay to
many
> places
> the code tries to do a classForName to check if it can continue to do its
> parsing -
> and by waaay to many, I mean waaay to many for me to go changing the parse
> semantics :(
>
> So, I'll try to "just" add the metadata tag stuff...that should be doable
> without changing much
> of the semantics, but it sure won't be as usable when the parser still
> requires the classes to
> be available ;(
>
> /max
>

Re: [Hibernate] Reference Doc Problems

[Gavin K. <ga...@ap...>]

Thanks. Fixed all those things, except for the default cascade-style, which
can depend upon the style defined on the root element.

----- Original Message -----
From: "Mark Woon" <mor...@SM...>
To: <hib...@li...>
Sent: Sunday, October 27, 2002 2:17 PM
Subject: [Hibernate] Reference Doc Problems


> Spotted a few errors/inconsistoncies in the reference doc:
>
> 1)  Instead of "cascade_style" use "all|none|save-update|delete".  Which
> is default?
> 2)  Still using "save/update" instead of "save-update"
> 3)  Is "usorted" in 'sort="usorted|natural|comparatorClass"' mispelled?
>  Should it be unsorted instead?
> 4)  hibernate.jdbc.batch_size uses true|false as opposed to number.  Is
> there a recommended size?  (BTW, Oracle says 5-30, 10 being a good place
> to start.)
>
>
> -Mark
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

[Hibernate] Reference Doc Problems

[Mark W. <mor...@SM...>]

Spotted a few errors/inconsistoncies in the reference doc:

1)  Instead of "cascade_style" use "all|none|save-update|delete".  Which 
is default?
2)  Still using "save/update" instead of "save-update"
3)  Is "usorted" in 'sort="usorted|natural|comparatorClass"' mispelled? 
 Should it be unsorted instead?
4)  hibernate.jdbc.batch_size uses true|false as opposed to number.  Is 
there a recommended size?  (BTW, Oracle says 5-30, 10 being a good place 
to start.)


-Mark

Re: [Hibernate] Suggestion: Utilize commons.lang.exception

[Gavin K. <ga...@ap...>]

Thanks; I had thought of doing this myself but couldn't get round to it.

I did a bit more cleaning up along the same lines.

Much nicer now.

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Sunday, October 27, 2002 9:11 AM
Subject: Re: [Hibernate] Suggestion: Utilize commons.lang.exception


> And as always - I could not wait so it is in the "Patches" on sourceforge
:)
>
> /max
>
> ----- Original Message -----
> From: "Max Rydahl Andersen" <ma...@eo...>
> To: <hib...@li...>
> Sent: Saturday, October 26, 2002 10:21 PM
> Subject: [Hibernate] Suggestion: Utilize commons.lang.exception
>
>
> > Hi!
> >
> > I will suggest that HibernateException et.al. should extend
> > commons.lang.exeception.NestableException, as hibernate is already
> dependent
> > on the commons.lang stuff.
> >
> > Why ?, because while working on "stress-testing" the error handling in
> some
> > of the parsing of the hibernate internals I found that if the cause/root
> > exception would have been included in the errorreporting I would have
much
> > more relevant information available to me as an hibernate user.
> >
> > If you say "yes - that's a great idea" then I'll gladly start on doing
the
> > footwork and send you the patch - but some people is quite
> > religous abut exception handling and the nestable "stuff", so if noone
> wants
> > to commit it to cvs I won't do it :)
> >
> > So, would you also like to get better error-messages in Hibernate ? yes
or
> > no ? :)
> >
> > /max
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: ApacheCon, November 18-21 in
> > Las Vegas (supported by COMDEX), the only Apache event to be
> > fully supported by the ASF. http://www.apachecon.com
> > _______________________________________________
> > hibernate-devel mailing list
> > hib...@li...
> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Re: [Hibernate] Suggestion: Utilize commons.lang.exception

[Max R. A. <ma...@eo...>]

And as always - I could not wait so it is in the "Patches" on sourceforge :)

/max

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Saturday, October 26, 2002 10:21 PM
Subject: [Hibernate] Suggestion: Utilize commons.lang.exception


> Hi!
>
> I will suggest that HibernateException et.al. should extend
> commons.lang.exeception.NestableException, as hibernate is already
dependent
> on the commons.lang stuff.
>
> Why ?, because while working on "stress-testing" the error handling in
some
> of the parsing of the hibernate internals I found that if the cause/root
> exception would have been included in the errorreporting I would have much
> more relevant information available to me as an hibernate user.
>
> If you say "yes - that's a great idea" then I'll gladly start on doing the
> footwork and send you the patch - but some people is quite
> religous abut exception handling and the nestable "stuff", so if noone
wants
> to commit it to cvs I won't do it :)
>
> So, would you also like to get better error-messages in Hibernate ? yes or
> no ? :)
>
> /max
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

[Hibernate] Suggestion: Utilize commons.lang.exception

[Max R. A. <ma...@eo...>]

Hi!

I will suggest that HibernateException et.al. should extend
commons.lang.exeception.NestableException, as hibernate is already dependent
on the commons.lang stuff.

Why ?, because while working on "stress-testing" the error handling in some
of the parsing of the hibernate internals I found that if the cause/root
exception would have been included in the errorreporting I would have much
more relevant information available to me as an hibernate user.

If you say "yes - that's a great idea" then I'll gladly start on doing the
footwork and send you the patch - but some people is quite
religous abut exception handling and the nestable "stuff", so if noone wants
to commit it to cvs I won't do it :)

So, would you also like to get better error-messages in Hibernate ? yes or
no ? :)

/max

Re: [Hibernate] Hibernate2UML

[Gavin K. <ga...@ap...>]

Yeah that would be cool. I think with the new *Metadata interfaces its also
quite easily doable. I don't know much about xmi myself but if you do, I
think you would be able to implement this quite straightforwardly....

----- Original Message -----
From: "Ampie Barnard" <amp...@mw...>
To: <hib...@li...>
Sent: Saturday, October 26, 2002 1:23 PM
Subject: [Hibernate] Hibernate2UML


> Just a thought
>
> Currently Hibernate allows me to generate java code and db schemas from my
> mapping file. It would be great if I could generate a UML class diagram
(in
> the form an xmi file ) from my mapping file. The mapping file is already
> rich in UML concepts like composition, aggregation, association, keyed and
> ordered relationships. Yet another indication how well Hibernate sticks to
> the OO paradigm!
>
> Personally my class diagrams seldom go into more detail than my
persistence
> model, but I do find that as we approach the deadline of a project, even
> these diagrams get out of sync with my code and the db. And then after
that
> I have the business analysts on my back asking all sorts of silly
questions,
> which they could answer for themselves if they understood my Hibernate
> mapping file, which will never get out of sync with my db and code.
>
> Ampie
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

[Hibernate] Hibernate2UML

[Ampie B. <amp...@mw...>]

Just a thought

Currently Hibernate allows me to generate java code and db schemas from my
mapping file. It would be great if I could generate a UML class diagram (in
the form an xmi file ) from my mapping file. The mapping file is already
rich in UML concepts like composition, aggregation, association, keyed and
ordered relationships. Yet another indication how well Hibernate sticks to
the OO paradigm!

Personally my class diagrams seldom go into more detail than my persistence
model, but I do find that as we approach the deadline of a project, even
these diagrams get out of sync with my code and the db. And then after that
I have the business analysts on my back asking all sorts of silly questions,
which they could answer for themselves if they understood my Hibernate
mapping file, which will never get out of sync with my db and code.

Ampie

[Hibernate] [PATCH] - Adding ShowSql attribute for HibernateServiceMBean

[Matt V. <mv...@ob...>]

  Adding ShowSql as an attribute for the HibernateServiceMBean. Patch is 
posted on the sourceforge site.

I am unable to do a diff on the jmx.html page do to the error I got  "\ 
No newline at end of file". Something to do with \n and \r!!! I have 
attached the jmx.html file with the updates.

Re: [Hibernate] Bug in CharacterType...

[Gavin K. <ga...@ap...>]

Woops yeah, I fixed it myself ... didn't get notified of the patch.

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: "Gavin King" <ga...@ap...>;
<hib...@li...>
Sent: Friday, October 25, 2002 9:54 PM
Subject: Re: [Hibernate] Bug in CharacterType...


> hehe - I asked on this list BECAUSE it was in the first CVS revision and
> had not changed since then - so I was not really sure if it was
intentional
> or not :)
>
> But now its fixed and my generic browser works again :)  (note: I have
also
> submitted a patch - so if
> you have checked something in, please update the patch tracking too :)
>
> /max
>
> p.s. looking forward to the prize :)
>
> ----- Original Message -----
> From: "Gavin King" <ga...@ap...>
> To: "Max Rydahl Andersen" <ma...@eo...>;
> <hib...@li...>
> Sent: Friday, October 25, 2002 1:48 PM
> Subject: Re: [Hibernate] Bug in CharacterType...
>
>
> > Wow, what an absolutely ancient bug!! Its in the very first CVS
revision.
> > Easy to see how it could slip through, though. I doubt many people have
> > properties of type java.lang.Character....
> >
> > You get some kind of prize for that.
> >
> > ----- Original Message -----
> > From: "Max Rydahl Andersen" <ma...@eo...>
> > To: <hib...@li...>
> > Sent: Friday, October 25, 2002 7:17 PM
> > Subject: [Hibernate] Bug in CharacterType...
> >
> >
> > > Hi!
> > >
> > > The following code is found in CharacterType:
> > > public Object get(ResultSet rs, String name) throws SQLException {
> > >
> > > return new Character(rs.getString(name).charAt(0));
> > >
> > > }
> > >
> > >
> > >
> > > Shouldn't this be something like the following to avoid a possible
null
> > > value ?!:
> > >
> > >  public Object get(ResultSet rs, String name) throws SQLException {
> > >
> > > String s = rs.getString(name);
> > >
> > > if(s!=null) {
> > >
> > > return new Character(s.charAt(0));
> > >
> > > } else {
> > >
> > > return null;
> > >
> > > }
> > >
> > > }
> > >
> > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by: Influence the future
> > > of Java(TM) technology. Join the Java Community
> > > Process(SM) (JCP(SM)) program now.
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> > > _______________________________________________
> > > hibernate-devel mailing list
> > > hib...@li...
> > > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >
> >

Re: [Hibernate] Bug in CharacterType...

[Max R. A. <ma...@eo...>]

hehe - I asked on this list BECAUSE it was in the first CVS revision and
had not changed since then - so I was not really sure if it was intentional
or not :)

But now its fixed and my generic browser works again :)  (note: I have also
submitted a patch - so if
you have checked something in, please update the patch tracking too :)

/max

p.s. looking forward to the prize :)

----- Original Message -----
From: "Gavin King" <ga...@ap...>
To: "Max Rydahl Andersen" <ma...@eo...>;
<hib...@li...>
Sent: Friday, October 25, 2002 1:48 PM
Subject: Re: [Hibernate] Bug in CharacterType...


> Wow, what an absolutely ancient bug!! Its in the very first CVS revision.
> Easy to see how it could slip through, though. I doubt many people have
> properties of type java.lang.Character....
>
> You get some kind of prize for that.
>
> ----- Original Message -----
> From: "Max Rydahl Andersen" <ma...@eo...>
> To: <hib...@li...>
> Sent: Friday, October 25, 2002 7:17 PM
> Subject: [Hibernate] Bug in CharacterType...
>
>
> > Hi!
> >
> > The following code is found in CharacterType:
> > public Object get(ResultSet rs, String name) throws SQLException {
> >
> > return new Character(rs.getString(name).charAt(0));
> >
> > }
> >
> >
> >
> > Shouldn't this be something like the following to avoid a possible null
> > value ?!:
> >
> >  public Object get(ResultSet rs, String name) throws SQLException {
> >
> > String s = rs.getString(name);
> >
> > if(s!=null) {
> >
> > return new Character(s.charAt(0));
> >
> > } else {
> >
> > return null;
> >
> > }
> >
> > }
> >
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: Influence the future
> > of Java(TM) technology. Join the Java Community
> > Process(SM) (JCP(SM)) program now.
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> > _______________________________________________
> > hibernate-devel mailing list
> > hib...@li...
> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
>

Re: [Hibernate] Bug in CharacterType...

[Gavin K. <ga...@ap...>]

Wow, what an absolutely ancient bug!! Its in the very first CVS revision.
Easy to see how it could slip through, though. I doubt many people have
properties of type java.lang.Character....

You get some kind of prize for that.

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: <hib...@li...>
Sent: Friday, October 25, 2002 7:17 PM
Subject: [Hibernate] Bug in CharacterType...


> Hi!
>
> The following code is found in CharacterType:
> public Object get(ResultSet rs, String name) throws SQLException {
>
> return new Character(rs.getString(name).charAt(0));
>
> }
>
>
>
> Shouldn't this be something like the following to avoid a possible null
> value ?!:
>
>  public Object get(ResultSet rs, String name) throws SQLException {
>
> String s = rs.getString(name);
>
> if(s!=null) {
>
> return new Character(s.charAt(0));
>
> } else {
>
> return null;
>
> }
>
> }
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

[Hibernate] Bug in CharacterType...

[Max R. A. <ma...@eo...>]

Hi!

The following code is found in CharacterType:
public Object get(ResultSet rs, String name) throws SQLException {

return new Character(rs.getString(name).charAt(0));

}



Shouldn't this be something like the following to avoid a possible null
value ?!:

 public Object get(ResultSet rs, String name) throws SQLException {

String s = rs.getString(name);

if(s!=null) {

return new Character(s.charAt(0));

} else {

return null;

}

}

Re: [Hibernate] Are types really needed for queries?

[Gavin K. <ga...@ap...>]

In general it can't figure out the type. Consider:

from foo in class Foo where foo.floatValue + 1 = ?
from foo in class Foo where someUserFunction( foo.value ) = ?

etc....

On the other hand, Query.setParameter() has some hueristics for guessing the
type from the given object, which is not 100% reliable, but its pretty good.
If we would have already had the Query interface when I designed the Session
interface, we could have made a good argument for letting the convenience
methods on Session use those same hueristics. But we didn't, so it wasn't an
option at the time.


----- Original Message -----
From: "Chris Nokleberg" <ch...@si...>
To: <hib...@li...>
Sent: Friday, October 25, 2002 5:40 AM
Subject: [Hibernate] Are types really needed for queries?


> Just a thought...shouldn't Hibernate be able to infer the Type or Type[]
> needed in find/findIdentifiers/iterate calls from the query itself?
>
> e.g.
>
> List moreCats = sess.find(
>     "from cat in class eg.Cat where " +
>     "cat.name = 'Fritz' or cat.id = ? or cat.id = ?",
>     new Object[] { id1, id2 },
>     new Type[] { Hibernate.LONG, Hibernate.LONG }
> );
>
> I think Hibernate already knows that these need to be LONGs.
>
> Maybe there are cases where there is some ambiguity, but if so I would
> guess it could be resolved by looking at the actual types of the
> argument objects (id1, id2).
>
> -Chris
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel