Menu
▾
▴
hibernate-issues
|
From: <leg...@at...> - 2004-09-07 22:26:08
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/browse/HB-1215 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-1215 Summary: Teradata Dialect Type: Improvement Status: Unassigned Priority: Major Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: Hibernate2 Assignee: Reporter: John Pianezze Created: Tue, 7 Sep 2004 5:56 PM Updated: Tue, 7 Sep 2004 5:56 PM Environment: hibernate 2.1.4 on JBoss 3.2.5 Description: The Teradata DBMS is not supported. I have implemented a dialect that supports the basic features of the database. Notes: Newer versions of teradata support "identity columns" but there's no way to know the value of the column that was generated, so you can't use it generate the ID column with Hibernate. It also does not support Sequence numbers, however you can implement a "teradata macro" to support it, and inthe dialect, you use the following syntax: execute hibernate_sequence(seq_name) with the sequence name as a parameter. One additional fix is required, as detailed in HB-1214 the JDBC code that runs the sequence query needs to be able to get the sequence number from a compound result set. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2004-09-07 22:32:02
|
The following issue has been updated:
Updater: John Pianezze (mailto:jpi...@te...)
Date: Tue, 7 Sep 2004 6:01 PM
Comment:
The code makes assumptions that a macro with a particular name exists, and that the macro only has one select statement that can return one or more results. a sample macro is provided.
Changes:
Attachment changed to TeradataDialect.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215?page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-1215
Summary: Teradata Dialect
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: Hibernate2
Assignee:
Reporter: John Pianezze
Created: Tue, 7 Sep 2004 5:56 PM
Updated: Tue, 7 Sep 2004 6:01 PM
Environment: hibernate 2.1.4 on JBoss 3.2.5
Description:
The Teradata DBMS is not supported.
I have implemented a dialect that supports the basic features of the database.
Notes: Newer versions of teradata support "identity columns" but there's no way to know the value of the column that was generated, so you can't use it generate the ID column with Hibernate.
It also does not support Sequence numbers, however you can implement a "teradata macro" to support it, and inthe dialect, you use the following syntax:
execute hibernate_sequence(seq_name)
with the sequence name as a parameter.
One additional fix is required, as detailed in HB-1214
the JDBC code that runs the sequence query needs to be able to get the sequence number from a compound result set.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-09-27 02:08:29
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@hi...)
Date: Sun, 26 Sep 2004 9:40 PM
Changes:
type changed from Improvement to Patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215?page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-1215
Summary: Teradata Dialect
Type: Patch
Status: Unassigned
Priority: Major
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: Hibernate2
Assignee:
Reporter: John Pianezze
Created: Tue, 7 Sep 2004 5:56 PM
Updated: Sun, 26 Sep 2004 9:40 PM
Environment: hibernate 2.1.4 on JBoss 3.2.5
Description:
The Teradata DBMS is not supported.
I have implemented a dialect that supports the basic features of the database.
Notes: Newer versions of teradata support "identity columns" but there's no way to know the value of the column that was generated, so you can't use it generate the ID column with Hibernate.
It also does not support Sequence numbers, however you can implement a "teradata macro" to support it, and inthe dialect, you use the following syntax:
execute hibernate_sequence(seq_name)
with the sequence name as a parameter.
One additional fix is required, as detailed in HB-1214
the JDBC code that runs the sequence query needs to be able to get the sequence number from a compound result set.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2004-09-27 03:16:14
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sun, 26 Sep 2004 10:48 PM
Body:
This Dialect does not seem to have any methods overriding DDL generation. Is Teradata *really* conforming to all the defaults defined by the superclass?? Has this been fully tested (incl. SchemaExport)?
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215?page=comments#action_14483
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1215
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-1215
Summary: Teradata Dialect
Type: Patch
Status: Unassigned
Priority: Major
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: Hibernate2
Assignee:
Reporter: John Pianezze
Created: Tue, 7 Sep 2004 5:56 PM
Updated: Sun, 26 Sep 2004 10:48 PM
Environment: hibernate 2.1.4 on JBoss 3.2.5
Description:
The Teradata DBMS is not supported.
I have implemented a dialect that supports the basic features of the database.
Notes: Newer versions of teradata support "identity columns" but there's no way to know the value of the column that was generated, so you can't use it generate the ID column with Hibernate.
It also does not support Sequence numbers, however you can implement a "teradata macro" to support it, and inthe dialect, you use the following syntax:
execute hibernate_sequence(seq_name)
with the sequence name as a parameter.
One additional fix is required, as detailed in HB-1214
the JDBC code that runs the sequence query needs to be able to get the sequence number from a compound result set.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: Todd N. (JIRA) <no...@at...> - 2006-05-24 16:52:16
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HB-1215?page=comments#action_23155 ] Todd Nine commented on HB-1215: ------------------------------- I need to implement a dialect for Tera Data, but I will be using Hibernate 3. As far as I can tell, TeraData's type 4 driver does not support any sort of metadata, should I just throw an UnsupportedOperationException for the DDL generation. > Teradata Dialect > ---------------- > > Key: HB-1215 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1215 > Project: Hibernate2 > Type: Patch > Environment: hibernate 2.1.4 on JBoss 3.2.5 > Reporter: John Pianezze > Attachments: TeradataDialect.java > > Original Estimate: 1 hour > Remaining: 1 hour > > The Teradata DBMS is not supported. > I have implemented a dialect that supports the basic features of the database. > Notes: Newer versions of teradata support "identity columns" but there's no way to know the value of the column that was generated, so you can't use it generate the ID column with Hibernate. > It also does not support Sequence numbers, however you can implement a "teradata macro" to support it, and inthe dialect, you use the following syntax: > execute hibernate_sequence(seq_name) > with the sequence name as a parameter. > One additional fix is required, as detailed in HB-1214 > the JDBC code that runs the sequence query needs to be able to get the sequence number from a compound result set. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X