Menu
▾
▴
nhibernate-issues
|
From: Jim H. J. (JIRA) <nh...@gm...> - 2011-01-31 23:02:22
|
Sybase ASE 15 support
---------------------
Key: NH-2526
URL: http://216.121.112.228/browse/NH-2526
Project: NHibernate
Issue Type: Improvement
Components: DataProviders / Dialects
Affects Versions: 3.0.0.GA
Reporter: Jim Hale Jr.
Priority: Major
Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
The 3.0.0 release banished Sybase ASE users for reasons unknown to me. I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate. Better to have basic but functional support than no support at all. This is especially important for ASE users considering the lack of Entity support by Sybase for ASE. Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider. The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me. ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers. Their dialects cannot be merged! Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase. I am using it in a project currently and it at least appears to work. I am only using the most basic of NHibernate features though so additional testing would be nice. But it provides a start.
Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Julian M. (JIRA) <nh...@gm...> - 2011-03-26 06:23:13
|
[ http://216.121.112.228/browse/NH-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Maughan reassigned NH-2526:
----------------------------------
Assignee: Julian Maughan
> Sybase ASE 15 support
> ---------------------
>
> Key: NH-2526
> URL: http://216.121.112.228/browse/NH-2526
> Project: NHibernate
> Issue Type: Improvement
> Components: DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Jim Hale Jr.
> Assignee: Julian Maughan
> Priority: Major
> Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
>
>
> The 3.0.0 release banished Sybase ASE users for reasons unknown to me. I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate. Better to have basic but functional support than no support at all. This is especially important for ASE users considering the lack of Entity support by Sybase for ASE. Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider. The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me. ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers. Their dialects cannot be merged! Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
> Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase. I am using it in a project currently and it at least appears to work. I am only using the most basic of NHibernate features though so additional testing would be nice. But it provides a start.
> Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Julian M. (JIRA) <nh...@gm...> - 2011-04-10 16:24:58
|
[ http://216.121.112.228/browse/NH-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Maughan resolved NH-2526.
--------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
Assignee: (was: Julian Maughan)
I've committed a driver and dialect for Sybase ASE 15 (r5649). I spent quite a bit of time messing about with it, and seeing how many tests would pass. One point I'm confused about is that the Hibernate version, and the attached, have support for temporary tables enabled. I found that ASE does not allow temporary tables to be created inside a transaction. This causes many test failures in NH, so I have disabled it in our dialect. See the code for more details.
> Sybase ASE 15 support
> ---------------------
>
> Key: NH-2526
> URL: http://216.121.112.228/browse/NH-2526
> Project: NHibernate
> Issue Type: Improvement
> Components: DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Jim Hale Jr.
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
>
>
> The 3.0.0 release banished Sybase ASE users for reasons unknown to me. I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate. Better to have basic but functional support than no support at all. This is especially important for ASE users considering the lack of Entity support by Sybase for ASE. Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider. The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me. ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers. Their dialects cannot be merged! Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
> Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase. I am using it in a project currently and it at least appears to work. I am only using the most basic of NHibernate features though so additional testing would be nice. But it provides a start.
> Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jim H. J. (JIRA) <nh...@gm...> - 2011-04-13 13:25:23
|
[ http://216.121.112.228/browse/NH-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20903#action_20903 ]
Jim Hale Jr. commented on NH-2526:
----------------------------------
You are correct - ASE 15 does choke on temp tables within transactions. Thanks for your work on this.
> Sybase ASE 15 support
> ---------------------
>
> Key: NH-2526
> URL: http://216.121.112.228/browse/NH-2526
> Project: NHibernate
> Issue Type: Improvement
> Components: DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Jim Hale Jr.
> Priority: Major
> Fix For: 3.2.0Alpha1
>
> Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
>
>
> The 3.0.0 release banished Sybase ASE users for reasons unknown to me. I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate. Better to have basic but functional support than no support at all. This is especially important for ASE users considering the lack of Entity support by Sybase for ASE. Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider. The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me. ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers. Their dialects cannot be merged! Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
> Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase. I am using it in a project currently and it at least appears to work. I am only using the most basic of NHibernate features though so additional testing would be nice. But it provides a start.
> Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Julian M. (JIRA) <nh...@gm...> - 2011-04-16 03:37:22
|
[ http://216.121.112.228/browse/NH-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20911#action_20911 ]
Julian Maughan commented on NH-2526:
------------------------------------
Not sure if you saw this, but in the code I commented that temp tables can be created outside a transaction by changing the 'ddl in tran' setting to true on the tempdb database. However, there are some fairly dire warnings about doing so, such as: "WARNING! Data definition language (DDL) commands hold locks on system tables such as sysobjects. Avoid using them inside transactions; if you must use them, keep the transactions short. Using any DDL commands on tempdb within transactions may cause your system to grind to a halt. Always leave ddl in tran set to false in tempdb."
Changing the setting did improve the number of test passes considerably. It doesn't make sense to me that temp tables would be handled like other DDL statements.
> Sybase ASE 15 support
> ---------------------
>
> Key: NH-2526
> URL: http://216.121.112.228/browse/NH-2526
> Project: NHibernate
> Issue Type: Improvement
> Components: DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Jim Hale Jr.
> Priority: Major
> Fix For: 3.2.0Alpha1
>
> Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
>
>
> The 3.0.0 release banished Sybase ASE users for reasons unknown to me. I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate. Better to have basic but functional support than no support at all. This is especially important for ASE users considering the lack of Entity support by Sybase for ASE. Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider. The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me. ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers. Their dialects cannot be merged! Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
> Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase. I am using it in a project currently and it at least appears to work. I am only using the most basic of NHibernate features though so additional testing would be nice. But it provides a start.
> Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/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