RE: [Hibernate] Some Wiki and Forum Suggestions
dres - oscache -Original Message- From: [EMAIL PROTECTED] [mailto:hibernate-devel- [EMAIL PROTECTED] On Behalf Of Christian Bauer Sent: Monday, February 14, 2005 2:32 AM To: Hibernate development Subject: Re: [Hibernate] Some Wiki and Forum Suggestions Michael Gloegl wrote: In the Wiki, the Cowiki text formating rules under the edit box is no longer pointing to the correct URL - it currently is http://www.develnet.org/95.html but should be http://cowiki.org/104.html Done Also in the forum, could we perhaps somehow mark the developers of projects we (directly or indirectly) depend on? For example give guys like Alin or the Proxool and cglib guys a special tag like jDTS developer? I think there is something like this in phpBB as far as I know. What do you think of that? If they tell me their project and nickname, sure. -- Christian Bauer callto://christian-bauer Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] http://jboss.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Re: API name changes
-Original Message- From: [EMAIL PROTECTED] [mailto:hibernate-devel- [EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Monday, February 14, 2005 3:16 AM To: hibernate-devel@lists.sourceforge.net Subject: Re: [Hibernate] Re: API name changes Christian Bauer wrote: Christian Bauer wrote: Starting with H3, we recommend the new EJB3-style operations create() and merge(). We still have our old methods: save(), update(), saveOrUpdate(), with slightly different semantics. What do you think about save(), attach(), saveOrAttach()? It might be too much code to change, but this is really our last chance to fix it and to help people think in object states, not SQL statements (something I repeat about 10 times during a Hibernate training). 'save' and 'attach' seems not coherent with each other, I'm not a big fan. -1 Again, I repeat this question. It's critical for our docs, training material, etc. Repeat: This is the last chance to make any changes. Even if you don't really have much to say about it, express your opinion please. Also, should we rename create() to persist() to be aligned with EJB3 EDR2? +1 +1 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Fix for OSCache clustering
I have a patch for the OSCache classes that are part of hibernate to fix the issues with clustering when using this provider. If you were not aware, the cluster listener is set up in oscache per cache instance. Since the provider was creating a cache for each region, it would fail in a clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry. Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region. So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you dont want it I dont really care. Just trying to help. -dres. - Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519
RE: [Hibernate] Fix for OSCache clustering
Just to clarify this does not eliminate the regions. It just corrects the way the provider implemented them. You can put and flush into the region. You can set different refresh periods and cron policies per region. You just cannot set a separate capacity. Oscache groups sort of = hibernate regions. I did notice that you did not recommend using OSCache in a cluster and when I asked why no one spoke up. Now I know that the provider implementation did not fit the design (however flawed) of oscache. Clustered invalidation is a real need but that is not oscache's only advantage. I really like the treecache but it is just not there yet for us and, I expect, others as well. -Original Message- From: Gavin King [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 4:12 PM To: March, Andres Cc: [EMAIL PROTECTED] Subject: Re: [Hibernate] Fix for OSCache clustering No, I'm not really interested in this patch. Entire assumption of Hibernate cache architecture is that we have various cache regions. You will notice that we don't recommend OSCache to be used in a cluster. March, Andres wrote: I have a patch for the OSCache classes that are part of hibernate to fix the issues with clustering when using this provider. If you were not aware, the cluster listener is set up in oscache per cache instance. Since the provider was creating a cache for each region, it would fail in a clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry. Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region. So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you don't want it I don't really care. Just trying to help. -dres. - Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519 -- Gavin King +61 410 534 454 +1 404 822 8349 callto://gavinking Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] http://jboss.com --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Polymorphic queries, where and order by
I'm sorry if I expand the subject a little. We pulled a patch off the forums some where that allows us to order by any association. I was wondering why this patch never got applied. It seems it would be useful in this situation as well. I am really uncomfortable using a patched hibernate because there are less eyes on it and it makes upgrading harder. I can submit the patch as we've applied it if you like. But also let me know if there is any reason for not allowing this type of functionality. It has been extremely useful to us in our searches as I think it would be to others. -Original Message- From: [EMAIL PROTECTED] [mailto:hibernate-devel- [EMAIL PROTECTED] On Behalf Of William Draï Sent: Tuesday, September 28, 2004 1:31 AM To: [EMAIL PROTECTED] Subject: [Hibernate] Polymorphic queries, where and order by Let's say we have the following (simplified) mapping : class name=A table=T property name=field1 type=string/ subclass name=B property name=field2 type=string/ /subclass /class Now we can execute any HQL query on the class A using the field1, for example from A a where a.field1 like 'anything%' or from A a order by a.field1 The problems come when we want to use the field2 with the same queries. Of couse in simple SQL it is possible to do select * from T order by field2 But in HQL, from A a order by a.field2 rightly fails because field2 is not defined for class A. This causes problems in sortable or filtered data tables where the user can sort or filter by any column he wants. There is currently only two options : - allowing to sort only on columns of class A : possible but my users won't be really happy - casting the query to class B when the user sorts on a column of class B : that means that the results count of the query is not the same when it is sorted than when it is not ; it completely breaks the semantics of sorting/filtering I understand it does not follow the OO approach of HQL but it would be really useful to have an additional syntax to allow using fields of the subclass in HQL queries, something like select a from A+ a order by a.field2, or maybe an option in the Query interface like query.setUseInheritedProperties(true). What do you think of this ? Note : this is an extension of the JIRA HB-792 and could allow to resolve this case in a better way William --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Polymorphic queries, where and order by
Found the JIRA issues where we got the patch (see: http://opensource.atlassian.com/projects/hibernate/browse/HB-132 and http://opensource.atlassian.com/projects/hibernate/browse/HB-822). We have been testing and using this patch for about a month. We will be going live with this if we cannot get it integrated into CVS. Obviously we prefer it get applied to CVS. Is there any reason something like this would be stalled. It seems like a minor patch for decent improvement in functionality. Anything I can do to get this in? From: Emmanuel Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 9:30 AM To: March, Andres Cc: [EMAIL PROTECTED] Subject: Re: [Hibernate] Polymorphic queries, where and order by Speaking from memory, Gavin did implement something on the (now dead 2.2 branch). It now has been reporded on H3. Did you test it? I can remembe, he'd implemented the transparent subclassing (no special keyword). March, Andres wrote: I'm sorry if I expand the subject a little. We pulled a patch off the forums some where that allows us to order by any association. I was wondering why this patch never got applied. It seems it would be useful in this situation as well. I am really uncomfortable using a patched hibernate because there are less eyes on it and it makes upgrading harder. I can submit the patch as we've applied it if you like. But also let me know if there is any reason for not allowing this type of functionality. It has been extremely useful to us in our searches as I think it would be to others. -Original Message-From: [EMAIL PROTECTED] [mailto:hibernate-devel-[EMAIL PROTECTED]] On Behalf Of William DraïSent: Tuesday, September 28, 2004 1:31 AMTo: [EMAIL PROTECTED]Subject: [Hibernate] Polymorphic queries, where and order byLet's say we have the following (simplified) mapping :class name=A table=T property name=field1 type=string/ subclass name=B property name=field2 type=string/ /subclass/classNow we can execute any HQL query on the class A using the field1, forexamplefrom A a where a.field1 like 'anything%' or from A a order by a.field1The problems come when we want to use the field2 with the same queries.Of couse in simple SQL it is possible to doselect * from T order by field2But in HQL, from A a order by a.field2 rightly fails because field2 isnot definedfor class A.This causes problems in sortable or filtered data tables where the usercan sort or filterby any column he wants.There is currently only two options :- allowing to sort only on columns of class A : possible but my userswon't be really happy- casting the query to class B when the user sorts on a column ofclass B : that means that the results count of the query is not the same when it is sorted than when it isnot ; it completely breaks the semantics of sorting/filteringI understand it does not follow the OO approach of HQL but it would bereally useful to have an additionalsyntax to allow using fields of the subclass in HQL queries, somethinglike select a from A+ a order by a.field2,or maybe an option in the Query interface likequery.setUseInheritedProperties(true).What do you think of this ?Note : this is an extension of the JIRA HB-792 and could allow toresolve this case in a better wayWilliam---This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170Project Admins to receive an Apple iPod Mini FREE for your judgement onwho ports your project to Linux PPC the best. Sponsored by IBM.Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php___hibernate-devel mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/hibernate-devel ---This SF.net email is sponsored by: IT Product Guide on ITManagersJournalUse IT products in your business? Tell us what you think of them. Give usYour Opinions, Get Free ThinkGeek Gift Certificates! Click to find out morehttp://productguide.itmanagersjournal.com/guidepromo.tmpl___hibernate-devel mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- Emmanuel Bernard01.55.21.52.14Fnac - DSIDirection France - Nouvelles technologies67, boulevard du Gal Leclerc92612 Clichy Cedex
RE: [Hibernate] Polymorphic queries, where and order by
Let me know if these are enough to get you going (see: http://opensource.atlassian.com/projects/hibernate/browse/HB-132 and http://opensource.atlassian.com/projects/hibernate/browse/HB-822 ). I am working on creating a more recent unified patch file. It would help to know if this will be well-received by the hibernate team. -Original Message- From: Raphael Jean [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 10:25 AM To: March, Andres Subject: RE: [Hibernate] Polymorphic queries, where and order by Hello, Would you be kind enough to either send me the patch you mention below, or let me know where I can find it? I have a similar problem in my application that this patch may solve. I haven't been able to find any information in the forum. Thanks in advance, Raphael Jean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of March, Andres Sent: mercredi 29 septembre 2004 17:59 To: [EMAIL PROTECTED] Subject: RE: [Hibernate] Polymorphic queries, where and order by I'm sorry if I expand the subject a little. We pulled a patch off the forums some where that allows us to order by any association. I was wondering why this patch never got applied. It seems it would be useful in this situation as well. I am really uncomfortable using a patched hibernate because there are less eyes on it and it makes upgrading harder. I can submit the patch as we've applied it if you like. But also let me know if there is any reason for not allowing this type of functionality. It has been extremely useful to us in our searches as I think it would be to others. -Original Message- From: [EMAIL PROTECTED] [mailto:hibernate- devel- [EMAIL PROTECTED] On Behalf Of William Draï Sent: Tuesday, September 28, 2004 1:31 AM To: [EMAIL PROTECTED] Subject: [Hibernate] Polymorphic queries, where and order by Let's say we have the following (simplified) mapping : class name=A table=T property name=field1 type=string/ subclass name=B property name=field2 type=string/ /subclass /class Now we can execute any HQL query on the class A using the field1, for example from A a where a.field1 like 'anything%' or from A a order by a.field1 The problems come when we want to use the field2 with the same queries. Of couse in simple SQL it is possible to do select * from T order by field2 But in HQL, from A a order by a.field2 rightly fails because field2 is not defined for class A. This causes problems in sortable or filtered data tables where the user can sort or filter by any column he wants. There is currently only two options : - allowing to sort only on columns of class A : possible but my users won't be really happy - casting the query to class B when the user sorts on a column of class B : that means that the results count of the query is not the same when it is sorted than when it is not ; it completely breaks the semantics of sorting/filtering I understand it does not follow the OO approach of HQL but it would be really useful to have an additional syntax to allow using fields of the subclass in HQL queries, something like select a from A+ a order by a.field2, or maybe an option in the Query interface like query.setUseInheritedProperties(true). What do you think of this ? Note : this is an extension of the JIRA HB-792 and could allow to resolve this case in a better way William --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https
RE: [Hibernate] Polymorphic queries, where and order by
We cant use H3 unfortunately because we do not have enough time to add H3 support to Spring. Is there any way this patch can be applied to H2? From: William Draï [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 11:22 AM To: Emmanuel Bernard Cc: March, Andres; [EMAIL PROTECTED] Subject: Re: [Hibernate] Polymorphic queries, where and order by I haven't yet tested with H3. I think there were no change logs related to this. I will try as soon as I have enough time. We can live without this feature for a few more weeks. Thank you for your anwser. Speaking from memory, Gavin did implement something on the (now dead 2.2 branch). It now has been reporded on H3. Did you test it? I can remembe, he'd implemented the transparent subclassing (no special keyword). March, Andres wrote: I'm sorry if I expand the subject a little. We pulled a patch off the forums some where that allows us to order by any association. I was wondering why this patch never got applied. It seems it would be useful in this situation as well. I am really uncomfortable using a patched hibernate because there are less eyes on it and it makes upgrading harder. I can submit the patch as we've applied it if you like. But also let me know if there is any reason for not allowing this type of functionality. It has been extremely useful to us in our searches as I think it would be to others. -Original Message-From: [EMAIL PROTECTED] [mailto:hibernate-devel-[EMAIL PROTECTED]] On Behalf Of William DraïSent: Tuesday, September 28, 2004 1:31 AMTo: [EMAIL PROTECTED]Subject: [Hibernate] Polymorphic queries, where and order byLet's say we have the following (simplified) mapping :class name=A table=T property name=field1 type=string/ subclass name=B property name=field2 type=string/ /subclass/classNow we can execute any HQL query on the class A using the field1, forexamplefrom A a where a.field1 like 'anything%' or from A a order by a.field1The problems come when we want to use the field2 with the same queries.Of couse in simple SQL it is possible to doselect * from T order by field2But in HQL, from A a order by a.field2 rightly fails because field2 isnot definedfor class A.This causes problems in sortable or filtered data tables where the usercan sort or filterby any column he wants.There is currently only two options :- allowing to sort only on columns of class A : possible but my userswon't be really happy- casting the query to class B when the user sorts on a column ofclass B : that means that the results count of the query is not the same when it is sorted than when it isnot ; it completely breaks the semantics of sorting/filteringI understand it does not follow the OO approach of HQL but it would bereally useful to have an additionalsyntax to allow using fields of the subclass in HQL queries, somethinglike select a from A+ a order by a.field2,or maybe an option in the Query interface likequery.setUseInheritedProperties(true).What do you think of this ?Note : this is an extension of the JIRA HB-792 and could allow toresolve this case in a better wayWilliam---This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170Project Admins to receive an Apple iPod Mini FREE for your judgement onwho ports your project to Linux PPC the best. Sponsored by IBM.Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php___hibernate-devel mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/hibernate-devel ---This SF.net email is sponsored by: IT Product Guide on ITManagersJournalUse IT products in your business? Tell us what you think of them. Give usYour Opinions, Get Free ThinkGeek Gift Certificates! Click to find out morehttp://productguide.itmanagersjournal.com/guidepromo.tmpl___hibernate-devel mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- Emmanuel Bernard01.55.21.52.14Fnac - DSIDirection France - Nouvelles technologies67, boulevard du Gal Leclerc92612 Clichy Cedex
RE: [Hibernate] Polymorphic queries, where and order by
Well, couldn't it be reclassified as a bug fix? Not being able to navigate associations because of a hard coded this in the construction of the order by seems like something many people would face. I could be wrong. Anyway this patch has been around a long time and as far as I can tell was submitted properly. More importantly H3 is not even released and support for it in Spring is even farther off. Any reason 2.1 is being abandoned so soon? I'm not asking for another 2.1 release. I don't see the harm in applying it to 2.1 CVS head but maybe I'm short-sighted. -Original Message- From: Emmanuel Bernard [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 12:59 PM To: March, Andres Cc: William Draï; Emmanuel Bernard; [EMAIL PROTECTED] Subject: Re: [Hibernate] Polymorphic queries, where and order by Sorry, no new feature will be added to the 2.1 branch. March, Andres wrote: We can't use H3 unfortunately because we do not have enough time to add H3 support to Spring. Is there any way this patch can be applied to H2? *From:* William Draï [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, September 29, 2004 11:22 AM *To:* Emmanuel Bernard *Cc:* March, Andres; [EMAIL PROTECTED] *Subject:* Re: [Hibernate] Polymorphic queries, where and order by I haven't yet tested with H3. I think there were no change logs related to this. I will try as soon as I have enough time. We can live without this feature for a few more weeks. Thank you for your anwser. Speaking from memory, Gavin did implement something on the (now dead 2.2 branch). It now has been reporded on H3. Did you test it? I can remembe, he'd implemented the transparent subclassing (no special keyword). March, Andres wrote: I'm sorry if I expand the subject a little. We pulled a patch off the forums some where that allows us to order by any association. I was wondering why this patch never got applied. It seems it would be useful in this situation as well. I am really uncomfortable using a patched hibernate because there are less eyes on it and it makes upgrading harder. I can submit the patch as we've applied it if you like. But also let me know if there is any reason for not allowing this type of functionality. It has been extremely useful to us in our searches as I think it would be to others. -Original Message- From: [EMAIL PROTECTED] mailto:hibernate- [EMAIL PROTECTED] [mailto:hibernate-devel- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] On Behalf Of William Draï Sent: Tuesday, September 28, 2004 1:31 AM To: [EMAIL PROTECTED] mailto:hibernate- [EMAIL PROTECTED] Subject: [Hibernate] Polymorphic queries, where and order by Let's say we have the following (simplified) mapping : class name=A table=T property name=field1 type=string/ subclass name=B property name=field2 type=string/ /subclass /class Now we can execute any HQL query on the class A using the field1, for example from A a where a.field1 like 'anything%' or from A a order by a.field1 The problems come when we want to use the field2 with the same queries. Of couse in simple SQL it is possible to do select * from T order by field2 But in HQL, from A a order by a.field2 rightly fails because field2 is not defined for class A. This causes problems in sortable or filtered data tables where the user can sort or filter by any column he wants. There is currently only two options : - allowing to sort only on columns of class A : possible but my users won't be really happy - casting the query to class B when the user sorts on a column of class B : that means that the results count of the query is not the same when it is sorted than when it is not ; it completely breaks the semantics of sorting/filtering I understand it does not follow the OO approach of HQL but it would be really useful to have an additional syntax to allow using fields of the subclass in HQL queries, something like select a from A+ a order by a.field2, or maybe an option in the Query interface like query.setUseInheritedProperties(true). What do you think of this ? Note : this is an extension of the JIRA HB-792 and could allow to resolve this case in a better way William --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ hibernate-devel mailing list [EMAIL PROTECTED] mailto:hibernate- [EMAIL PROTECTED
RE: [Hibernate] Hibernate 3.0 alpha ready for testing
Sounds great. Just wondering if there are any performance improvements that have been made or is this generally a feature release? -Original Message- From: [EMAIL PROTECTED] [mailto:hibernate-devel- [EMAIL PROTECTED] On Behalf Of Christian Bauer Sent: Tuesday, August 24, 2004 4:14 AM To: [EMAIL PROTECTED] Subject: [Hibernate] Hibernate 3.0 alpha ready for testing Hibernate3 is the world's most sophisticated ORM solution. Building on Hibernate 2.1, the de facto standard ORM implementation for Java, Hibernate3 adds a wealth of new features including: filters for handling temporal, regional and permissioned data, support for mixing hand-written and generated SQL, new options for mapping exotic inheritance strategies and legacy data, runtime performance monitoring via JMX, and a new event-driven architecture. See the road map for more details and have a look at the Changelog. The Hibernate3 core is 50 000 lines of open source Java code, released under the LGPL. Hibernate 3.0 alpha, which has been under development for almost a year, is now (available for download. A huge thanks to everyone who made this release possible. Note that this is an alpha-quality preview release. Please report any issues via JIRA. -- Christian Bauer +49 171 455 66 53 callto://christian-bauer Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] http://jboss.com --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: Re[2]: [Hibernate] Oracle stored procedures
Can't we just solve this with an XML configuration option? We could specify the Type
we need to get through reflection. We could even specify to use execute() or
executeQuery() through the configuration. Isn't it is better than hacking up the
code? I would gladly do it myself and submit a patch. Could you just point me to the
package/class that it would best fit into?
I know the JDBC implementers could have done it different ways but I think providing a
way to specify which out parameter to get the resultset from should be a feature. And
specifying in the XML mapping which type (eg. OracleTypes.CURSOR) to use doesn't seem
like a big deal either. But let me know if I'm wrong about that.
Note: http://forum.hibernate.org/viewtopic.php?t=11highlight=stored+procedure
Seems like someone did some work on this. Did they submit it to cvs or somewhere so I
don't have to start from scratch?
-Original Message-
From: Max Rydahl Andersen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 3:07 PM
To: March, Andres
Cc: [EMAIL PROTECTED]
Subject: Re[2]: [Hibernate] Oracle stored procedures
Hello Andres,
The problem as you yourself mention is that it is Oracle specific (as
it require an import com.oracle.jdbc.OracleTypes)
In MS SQL Server, DB2, Interbase, Sybase, Informix you can (more or
less) do
CallableStatement st = null;
ResultSet rs = null;
st = session.connection().prepareCall({call ? := ...});
st.setObject(2, optionalID);
rs = st.executeQuery();
Which would be MUUCH nice since then the existing executeQuery() calls
in hibernate core would work nicely without any tweaks!
Im the only one looking into this at the moment, but you are more than
welcome to see if you can find a better way out of this just for
oracle tweak.any contribution will be welcome ;)
/max
Tuesday, June 15, 2004, 11:39:55 PM, you wrote:
This seems to work for me. Obviously this is oracle specific but
we can make it extensible. I can write all the oracle specific code
for this, if necessary. I just don't want to have to deal with
resultsets anymore. I have not checked out the latest Hibernate3
from CVS yet. I will check it out. Please let me know if someone
has gone down this path already.
-Andres.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
March, Andres
Sent: Tuesday, June 15, 2004 2:09 PM
To: Max Rydahl Andersen
Cc: [EMAIL PROTECTED]
Subject: RE: [Hibernate] Oracle stored procedures
I saw this on the forums. Does it not work?
CallableStatement st = null;
ResultSet rs = null;
st = session.connection().prepareCall({call ? := ...});
st.registerOutParameter(1, OracleTypes.CURSOR);
st.setObject(2, optionalID);
st.execute();
rs = (ResultSet)st.getObject(1);
- Andres
-Original Message-
From: Max Rydahl Andersen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 1:53 PM
To: March, Andres
Cc: [EMAIL PROTECTED]
Subject: Re: [Hibernate] Oracle stored procedures
Hello Andres,
Tuesday, June 15, 2004, 5:49:06 PM, you wrote:
I was wondering if there is any progress being made ongetting
Oracle stored procedures working with hibernate CRUD queries. I
wouldlike to help out in this area if possible. One of the things I
would like tobe able to do is specify one of the out parameters to
be used as the resultset.
Hibernate3 has support for CUD operations in stored procedures.
R as in Read has not been implemented as at the moment the team
haven't found a good way (read standard) to get a out parameter as a
resultset.
Do you know a way ? ;)
(note: it actually seems like Oracle is the only major player who
don't have proper out parameter as resultset support - which I find
kind of weird ;)
/max
-
Andres March
Platform - Apps Engineering
Sony Online Entertainment
desk: 858.577.3373
cell: 619.519.1519
--
Best regards,
Maxmailto:[EMAIL PROTECTED]
---
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: Re[4]: [Hibernate] Oracle stored procedures
-Original Message-
From: Max Rydahl Andersen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 3:56 PM
To: March, Andres
Cc: [EMAIL PROTECTED]
Subject: Re[4]: [Hibernate] Oracle stored procedures
Hello Andres,
Wednesday, June 16, 2004, 12:41:39 AM, you wrote:
Can't we just solve this with an XML configuration option?
Putting the configuration option in xml does not solve the problem!
You need something in the code that handles the option!
I understand. I was just suggesting that the code written would not have to directly
reference driver specific types.
The right place to put it is in the Dialect since it is Dialect
specific!
I will check that out.
Note ALL other db's besides oracle can return resultsets via
executeQuery() which is the standard way inside hibernate core to get
a resultset.
I am looking into if it is possible to write the stored proc to do just that.
And it get's messy since you both have to something different with the
statement before and after calling execute on the statementand
those parts of hibernate does not know wether a statement is a sql or
stored procedure call.
This is the part I am most worried about.
We
could specify the Type we need to get through reflection. We could
even specify to use execute() or executeQuery() through the
configuration. Isn't it is better than hacking up the code?
Dude, you still need to change the code to support the option... ;)
Again, I know I'm looking to change the code. I just thought it best to abstract some
of these things out.
I
would gladly do it myself and submit a patch. Could you just point
me to the package/class that it would best fit into?
follow the forun thread as the user is on the right track - but do it
in hibernate3!
Looking at org.hibernate.impl.BatcherImpl now, is this where all the loader statements
are prepared or am I on the wrong track?
Note:
http://forum.hibernate.org/viewtopic.php?t=11highlight=stored+procedure
Seems like someone did some work on this. Did they submit it to
cvs or somewhere so I don't have to start from scratch?
the user never returned with a patch or answer
leech.
I know the JDBC implementers could have done it different ways
but I think providing a way to specify which out parameter to get
the resultset from should be a feature. And specifying in the XML
mapping which type (eg. OracleTypes.CURSOR) to use doesn't seem like
a big deal either. But let me know if I'm wrong about that.
Remember - it is ONLY oracle that has this misfeature ... and do you
have stored procedures that has more than one out parameter (namely
the first one) when you return a resultset ?
I am going to spend more time with the Oracle folks to see if I can find a way of
doing it like other dbs can. Even if we can't support all use cases, if we support 1
that is db independent, it seems worth it to me.
Best regards,
Max
Thanks for your input. Let me know if you have anymore.
-Original Message-
From: Max Rydahl Andersen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 3:07 PM
To: March, Andres
Cc: [EMAIL PROTECTED]
Subject: Re[2]: [Hibernate] Oracle stored procedures
Hello Andres,
The problem as you yourself mention is that it is Oracle specific (as
it require an import com.oracle.jdbc.OracleTypes)
In MS SQL Server, DB2, Interbase, Sybase, Informix you can (more or
less) do
CallableStatement st = null;
ResultSet rs = null;
st = session.connection().prepareCall({call ? := ...});
st.setObject(2, optionalID);
rs = st.executeQuery();
Which would be MUUCH nice since then the existing executeQuery() calls
in hibernate core would work nicely without any tweaks!
Im the only one looking into this at the moment, but you are more than
welcome to see if you can find a better way out of this just for
oracle tweak.any contribution will be welcome ;)
/max
Tuesday, June 15, 2004, 11:39:55 PM, you wrote:
This seems to work for me. Obviously this is oracle specific but
we can make it extensible. I can write all the oracle specific code
for this, if necessary. I just don't want to have to deal with
resultsets anymore. I have not checked out the latest Hibernate3
from CVS yet. I will check it out. Please let me know if someone
has gone down this path already.
-Andres.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
March, Andres
Sent: Tuesday, June 15, 2004 2:09 PM
To: Max Rydahl Andersen
Cc: [EMAIL PROTECTED]
Subject: RE: [Hibernate] Oracle stored procedures
I saw this on the forums. Does it not work?
CallableStatement st = null;
ResultSet rs = null;
st = session.connection().prepareCall({call ? := ...});
st.registerOutParameter(1, OracleTypes.CURSOR);
st.setObject(2, optionalID);
st.execute();
rs = (ResultSet)st.getObject(1
