[Hibernate] RE : [Hibernate] livelink collections server
Hello, The livelink product handles n to n relationship without intermediate table but with a field with multiple values. Is it possible to instruct Hibernate to comply to this? if so how do I do it? via the dialect? Regards, Ced. Message d'origine De: Steve Ebersole [mailto:[EMAIL PROTECTED] Date: mar. 24.01.2006 17:58 À: Bompart Cedric; hibernate-devel@lists.sourceforge.net Cc: Objet: RE: [Hibernate] livelink collections server A custom Dialect should be enough, although you may need to appropriately set some configuration properties as well... The best thing to do is to simply try running the Hibernate test suite using your custom dialect; that'll give you an idea of what type/level of SQL support Hibernate is expecting that this particular database may/may not provide. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bompart Cedric Sent: Tuesday, January 24, 2006 3:56 AM To: hibernate-devel@lists.sourceforge.net Subject: [Hibernate] livelink collections server Hello, I'm just wondering what do I need to do to support another database vendor with Hibernate 3.1 ? The database is LiveLink Collections Server from OpenText (known previously as Basis) and they provide a JDBC driver. So far I've seen that I need to write a new implementation of org.hibernate.dialect.Dialect and what else ? any documentation related to that subject ? or anything to look at will be nice... :-) Regards, Ced. -- M. Cedric Bompart J2EE Architect THALES Suisse SA --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] default HEM key generator
This is planned for Hibernate 3.2 Bill Burke wrote: Can we have a default HEM key generator that will not force an insert when using FlushMode.NEVER? Like Table or Sequence or some other hibernate specific generator? I've been working through some example applications for my book and am finding that I have to modify pre-existing entity code to use a table generator because I want to take advantage of the FlushMode.NEVER semantics. Bill --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
which it isn't afaik. the antlr version started to include more data in the exception over time. Including additional data is not an incompatible serialzable change generally. Its optional data that will be ignored and cannot affect the legacy implementation. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. True, but this can be handled by wrapping the stacktrace in a generic exception whose msg is the cause stacktrace. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? Dealing with incorrect serialization implementation via hacks at the serialization layer is not a scalable solution. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
The thing that we discussed (and I have just not yet had time to implement) is actually converting QueryExceptions that contain antlr stuff during serialization by either writeReplace() or writeObject(). Initially we had discussed just stripping the cause in the case of antrl exception, but perhaps another option is to simply write a replacement for the antlr exception during writeObject() on the QueryException. Yet another option would be to handle this as we recognize antrl exceptions in the translator/parser and decompose that information. I don't think the stack trace of the antlr exceptions themselves are really that vital to users anyway so we could just log the antlr exceptions for debug purposes. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 2:02 PM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark [EMAIL PROTECTED] wrote: fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. which it isn't afaik. the antlr version started to include more data in the exception over time. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the cause. Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Do antlr exception leak to users?
Hi, antlr exceptions can probably be contained by some of the methods mentioned below - no problem. I'm just wondering what to do with other exceptions ? They will have the same/similar problem correct? e.g. a ocracle driver specific exception occurs which is pretty good to have as the cause...that will spill to other clients too. /max The thing that we discussed (and I have just not yet had time to implement) is actually converting QueryExceptions that contain antlr stuff during serialization by either writeReplace() or writeObject(). Initially we had discussed just stripping the cause in the case of antrl exception, but perhaps another option is to simply write a replacement for the antlr exception during writeObject() on the QueryException. Yet another option would be to handle this as we recognize antrl exceptions in the translator/parser and decompose that information. I don't think the stack trace of the antlr exceptions themselves are really that vital to users anyway so we could just log the antlr exceptions for debug purposes. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 2:02 PM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark [EMAIL PROTECTED] wrote: fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. which it isn't afaik. the antlr version started to include more data in the exception over time. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the cause. Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
Well I think the distinction here is that Hibernate constitutes a hard dependency on Antlr. The users choice to use Oracle is completely within their control. -Original Message- From: Max Andersen Sent: Wednesday, February 08, 2006 8:41 AM To: Steve Ebersole; Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? Hi, antlr exceptions can probably be contained by some of the methods mentioned below - no problem. I'm just wondering what to do with other exceptions ? They will have the same/similar problem correct? e.g. a ocracle driver specific exception occurs which is pretty good to have as the cause...that will spill to other clients too. /max The thing that we discussed (and I have just not yet had time to implement) is actually converting QueryExceptions that contain antlr stuff during serialization by either writeReplace() or writeObject(). Initially we had discussed just stripping the cause in the case of antrl exception, but perhaps another option is to simply write a replacement for the antlr exception during writeObject() on the QueryException. Yet another option would be to handle this as we recognize antrl exceptions in the translator/parser and decompose that information. I don't think the stack trace of the antlr exceptions themselves are really that vital to users anyway so we could just log the antlr exceptions for debug purposes. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 2:02 PM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark [EMAIL PROTECTED] wrote: fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. which it isn't afaik. the antlr version started to include more data in the exception over time. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the cause. Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Do antlr exception leak to users?
On Wed, 08 Feb 2006 15:51:49 +0100, Steve Ebersole [EMAIL PROTECTED] wrote: Well I think the distinction here is that Hibernate constitutes a hard dependency on Antlr. The users choice to use Oracle is completely within their control. Fair reasoning. /max -Original Message- From: Max Andersen Sent: Wednesday, February 08, 2006 8:41 AM To: Steve Ebersole; Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? Hi, antlr exceptions can probably be contained by some of the methods mentioned below - no problem. I'm just wondering what to do with other exceptions ? They will have the same/similar problem correct? e.g. a ocracle driver specific exception occurs which is pretty good to have as the cause...that will spill to other clients too. /max The thing that we discussed (and I have just not yet had time to implement) is actually converting QueryExceptions that contain antlr stuff during serialization by either writeReplace() or writeObject(). Initially we had discussed just stripping the cause in the case of antrl exception, but perhaps another option is to simply write a replacement for the antlr exception during writeObject() on the QueryException. Yet another option would be to handle this as we recognize antrl exceptions in the translator/parser and decompose that information. I don't think the stack trace of the antlr exceptions themselves are really that vital to users anyway so we could just log the antlr exceptions for debug purposes. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 2:02 PM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark [EMAIL PROTECTED] wrote: fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. which it isn't afaik. the antlr version started to include more data in the exception over time. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the cause. Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] livelink collections server
What does the SQL look like to access this? -Original Message- From: Bompart Cedric [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 08, 2006 3:40 AM To: Steve Ebersole; hibernate-devel@lists.sourceforge.net Subject: RE : [Hibernate] livelink collections server Hello, The livelink product handles n to n relationship without intermediate table but with a field with multiple values. Is it possible to instruct Hibernate to comply to this? if so how do I do it? via the dialect? Regards, Ced. Message d'origine De: Steve Ebersole [mailto:[EMAIL PROTECTED] Date: mar. 24.01.2006 17:58 À: Bompart Cedric; hibernate-devel@lists.sourceforge.net Cc: Objet: RE: [Hibernate] livelink collections server A custom Dialect should be enough, although you may need to appropriately set some configuration properties as well... The best thing to do is to simply try running the Hibernate test suite using your custom dialect; that'll give you an idea of what type/level of SQL support Hibernate is expecting that this particular database may/may not provide. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bompart Cedric Sent: Tuesday, January 24, 2006 3:56 AM To: hibernate-devel@lists.sourceforge.net Subject: [Hibernate] livelink collections server Hello, I'm just wondering what do I need to do to support another database vendor with Hibernate 3.1 ? The database is LiveLink Collections Server from OpenText (known previously as Basis) and they provide a JDBC driver. So far I've seen that I need to write a new implementation of org.hibernate.dialect.Dialect and what else ? any documentation related to that subject ? or anything to look at will be nice... :-) Regards, Ced. -- M. Cedric Bompart J2EE Architect THALES Suisse SA --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
Right. The issue is we can't have the infinite web of project implementation details leaking to users unncessarily. Hibernate is a little different in that its used both in Java SE and Java EE profiles. My concern is that a pure Java EE client should not care about that antlr happens to be used for the ejb3 query language parser. Antlr should not be a required jar in the jboss client jars for ejb3 usage. -Original Message- From: Steve Ebersole Sent: Wednesday, February 08, 2006 6:52 AM To: Max Andersen; Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: RE: [Hibernate] Do antlr exception leak to users? Well I think the distinction here is that Hibernate constitutes a hard dependency on Antlr. The users choice to use Oracle is completely within their control. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
