[Hibernate-JIRA] Closed: (HHH-1063) support for 'locate' function in SQLServer and Sybase dialects
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1063?page=c... ]
Steve Ebersole closed HHH-1063.
-------------------------------
Closing stale resolved issues
> support for 'locate' function in SQLServer and Sybase dialects
> --------------------------------------------------------------
>
> Key: HHH-1063
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1063
> Project: Hibernate Core
> …
[View More] Issue Type: Patch
> Components: core
> Affects Versions: 3.1 rc2
> Environment: latest from CVS, SQL Server 2000
> Reporter: Nathan Moon
> Assignee: Gavin King
> Fix For: 3.1 rc3
>
> Attachments: CharindexFunction.java, SQLServerDialect.patch, sybasedialect.patch
>
>
> This is really 2 separate patches:
> 1. the file 'sqlserverdialect.patch' adds support for the 'locate' function in SQL Server 2000. Sybase doesn't seem to support a three param version of charindex, which is why this patch goes in SQLServerDialect and not in SybaseDialect.
> 2. the file 'sybasedialect.patch', along with the new file 'CharindexFunction.java' (belongs in org.hibernate.dialect.function), add support for the 'locate' function in Sybase (untested). I am not a Sybase user, but this seems like it should work to emulate the three param version of locate, even though Sybase doesn't seem to support a third param (start_index). To test this, I tried out something similar on SQLServer, but like I said, it's not really tested on Sybase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
13 years, 11 months
[Hibernate-JIRA] Closed: (HHH-608) update HSQLDialect for HSQL 1.8 sequence support
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-608?page=co... ]
Steve Ebersole closed HHH-608.
------------------------------
Closing stale resolved issues
> update HSQLDialect for HSQL 1.8 sequence support
> ------------------------------------------------
>
> Key: HHH-608
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-608
> Project: Hibernate Core
> Issue Type: Improvement
…
[View More]> Components: core
> Environment: Hibernate 3.0.5
> HSQLDB 1.8.0 RC 10
> Reporter: Christian Stein
> Assignee: Steve Ebersole
> Fix For: 3.1 rc 1
>
> Attachments: hibernate3modified.jar, HSQLDialect.java, HSQLDialect.java, HSQLDialect.patch, HSQLDialect.patch, TestHSQLDialectPatch.java
>
>
> ----- Original Message -----
> From: "Christian Stein" <sormuras(a)gmx.de>
> To: <fredt(a)users.sourceforge.net>
> Sent: 11 June 2005 05:40
> Subject: [HSQLDB-rc10] ...and Hibernate 3.0.5
> Hello Fred,
> when using the SchemaUpdate tool of Hibernate 3, it reports that it can't find the system table named "system_sequences". Is this table gone or not longer visible? I attached the stack trace first, and the interesting parts of the "HSQLDialect" class from the Hibernate source.
> Cheers,
> Christian
> === stack trace ===
> INFO [main] SchemaUpdate - Running hbm2ddl schema update
> INFO [main] SchemaUpdate - fetching database metadata
> ERROR [main] SchemaUpdate - could not get database metadata
> java.sql.SQLException:
> Table not found in statement [select sequence_name from system_sequences]
> org.hsqldb.jdbc.Util.sqlException(Unknown Source)
> org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
> org.hsqldb.jdbc.jdbcStatement.executeQuery(Unknown Source)
> org.hibernate.tool.hbm2ddl.DatabaseMetadata.initSequences(DatabaseMetadata.java:113)
> org.hibernate.tool.hbm2ddl.DatabaseMetadata.<init>(DatabaseMetadata.java:39)
> org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:124)
> === org.hibernate.dialect.HSQLDialect snippet ===
> public boolean supportsSequences() {
> return true;
> }
> public String getQuerySequencesString() {
> return "select sequence_name from system_sequences";
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
13 years, 11 months
[Hibernate-JIRA] Closed: (HHH-1200) Using formula-based property causes invalid SQL code for children "subselect" query
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1200?page=c... ]
Steve Ebersole closed HHH-1200.
-------------------------------
Closing stale resolved issues
> Using formula-based property causes invalid SQL code for children "subselect" query
> -----------------------------------------------------------------------------------
>
> Key: HHH-1200
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1200
> …
[View More] Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.1 rc3
> Environment: Hibernate 3.0.5, Hibernate 3.1rc3
> Oracle 8i
> Reporter: Serge P. Nekoval
>
> I have simple one-to-many relationship, mapped as set:
> <class name="Parent">
> <set name="children" lazy="false" fetch="subselect">
> <key column="PARENT_OID"/>
> <one-to-many class="Child"/>
> </set>
> </class>
> this works fine, constructing subselect SQL which looks like (e.g. for HQL query "from Parent"):
> select <child fields> from <child table> where child.PARENT_OID in (select this_.OID from PARENT this_)
> (simplified)
> However, when adding a formula-based property into Parent:
> <property name="myFormulaField" formula="(complex_select )"/>
> Now SQL becomes:
> select <child fields> from <child table> where PARENT_OID in (complex_select) as formula0_1_, <some parent fields> from PARENT this_)
> This SQL fails because of incorrect grammar (it also seems that backet is missing).
> This is something weird, because subselect fetching only needs Parent's identity column, not any other properties. And I don't think it should be affected by Parent's formula-based properties.
> I can provide more details if necessary, I stripped out all extra mapping/SQL stuff because it seems to be irrelevant here.
> This bug appeared in 3.0.5 later I've downloaded 3.1rc3 and it also fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
13 years, 11 months
[Hibernate-JIRA] Closed: (HHH-607) Save a new Object and the version is set to 1 instead of 0
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-607?page=co... ]
Steve Ebersole closed HHH-607.
------------------------------
Closing stale resolved issues
> Save a new Object and the version is set to 1 instead of 0
> ----------------------------------------------------------
>
> Key: HHH-607
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-607
> Project: Hibernate Core
> Issue …
[View More]Type: Bug
> Components: core
> Environment: Postgress, Windows XP
> Reporter: Julien Vallet
>
> Hi,
> I have made a class like this:
> public class TestVersionCounter
> {
> public TestVersionCounter()
> {
> }
> public Blob getConverted_serializableUserObjectTypedCollection()
> {
> return HibernateConverterSet.convertSerializableUserObjectTypedCollection(serializableUserObjectTypedCollection);
> }
> public void setConverted_serializableUserObjectTypedCollection(Blob aBlob)
> {
> try
> {
> serializableUserObjectTypedCollection=(SerializableUserObjectTypedCollection)SerializationHelper.deserialize(aBlob.getBinaryStream());
> }
> catch (Throwable throwable)
> {
>
> }
> }
> public Long getInternalKey()
> {
> return internalKey;
> }
> public void setInternalKey(Long theInternalKey)
> {
> internalKey=theInternalKey;
> }
> public String getName()
> {
> return name;
> }
> public void setName(String theName)
> {
> name=theName;
> }
> public int getVersionCounter()
> {
> return versionCounter;
> }
> public void setVersionCounter(int theVersionCounter)
> {
> versionCounter=theVersionCounter;
> }
> protected SerializableUserObjectTypedCollection serializableUserObjectTypedCollection;
> private Blob converted_serializableUserObjectTypedCollection;
> private String name=null;
> private Long internalKey=null;
> private int versionCounter=0;
> }
> with a mapping like this:
> <class name="com.sgcib.ibd.opp.tests.TestVersionCounter" table="TTestVersionCounterOPP" lazy="false" >
> <id name="internalKey" >
> <generator class="assigned" />
> </id>
> <version name="versionCounter" column="version" type="int" />
> <property name="name" column="name" length="255" />
> <property name="converted_serializableUserObjectTypedCollection" column="serializableUserObjectT" />
> </class>
> When I do
> TestVersionCounter testVersion=new TestVersionCounter();
> session.save(userObject);
> the version saved in the Database is 1 and not 0.
> Do you think this is a normal behaviour ?
> Thank you
> Regards.
> Julien.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
13 years, 11 months