Menu
▾
▴
hibernate-issues
|
From: <leg...@at...> - 2003-08-26 18:23:28
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 26 Aug 2003 1:22 PM
Body:
OK, so what I suggest is that we add a FirebirdDialect that (for now) extends InterbaseDialect. Would you please tell me exactly what differences there are; ie. what changes need to be made.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Tue, 26 Aug 2003 6:46 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-08-27 07:46:28
|
The following comment has been added to this issue:
Author: Reha CENANI
Created: Wed, 27 Aug 2003 2:45 AM
Body:
Regarding the select limit issues, please find below the explanations from their documentations.
*** For Firebird: ***
SELECT [FIRST (<integer expr m>)] [SKIP (<integer expr n>)] ...
Retrieves the first m rows of the selected output set. The optional SKIP clause will cause the first n rows to be discarded and return an output set of m rows starting at n + 1. In the simplest form, m and n are integers but any Firebird expression that evaluates to an integer is valid. Parentheses are required for expression arguments and optional otherwise.
bindLimitParametersFirst() --> true
bindLimitParametersInReverseOrder() --> true
*** For InterBase: ***
SELECT ... [ROWS <value> [TO <upper_value>] [BY <step_value>] [PERCENT] [WITH TIES]]
* <value> is the total number of rows to return if used by itself
* <value> is the starting row number to return if used with TO
* <value> is the percent if used with PERCENT
* <upper_value> is the last row or highest percent to return
* If <step_value> = n, returns every n'th row, or n percent rows
* PERCENT causes all previous ROWS values to be interpreted as percents
* WITH TIES returns additional duplicate rows when the last value in the ordered sequence is the same as values in subsequent rows of the result set; must be used in conjunction with ORDER BY
bindLimitParametersFirst() --> false
bindLimitParametersInReverseOrder() --> false
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Tue, 26 Aug 2003 6:46 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-08-27 09:46:28
|
The following comment has been added to this issue:
Author: Reha CENANI
Created: Wed, 27 Aug 2003 4:45 AM
Body:
Regarding the Sequence value and string issues:
*** Common ***
supportsSequences() --> true
getCreateSequenceString(String sequenceName) -->
"CREATE GENERATOR " + sequenceName
getSequenceNextValString(String sequenceName) -->
"SELECT GEN_ID(" + sequenceName + ", 1) FROM RDB$DATABASE"
*** For Firebird: ***
getDropSequenceString(String sequenceName) -->
"DROP GENERATOR " + sequenceName
*** For InterBase: ***
getDropSequenceString(String sequenceName) -->
"DELETE FROM RDB$GENERATORS WHERE RDB$GENERATOR_NAME = '" + sequenceName.toUpperCase() + "'"
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Tue, 26 Aug 2003 6:46 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-08-27 10:38:29
|
The following comment has been added to this issue:
Author: Reha CENANI
Created: Wed, 27 Aug 2003 5:37 AM
Body:
Regarding the For Update [Of] issues:
*** Common ***
supportsForUpdate() --> true
supportsForUpdateOf() --> true
supportsForUpdateNowait() --> false
*** For Firebird: ***
SELECT ... [FOR UPDATE [OF col [, col ...]]] [WITH LOCK]]
About optional [WITH LOCK]:
Firebird is an optimistic-locking system. The need for a pessimistic lock in Firebird is very rare indeed.
The addition of the optional WITH LOCK clause provides a limited explicit pessimistic locking capability for cautious use in conditions where the affected row set is a) extremely small (ideally, a singleton) and b) precisely controlled by the application code.
If the WITH LOCK clause succeeds, it will secure a lock on the selected rows and prevent any other transaction from obtaining write access to any of those rows, or their dependents, until your transaction ends.
If the FOR UPDATE clause is included, the lock will be applied to each row, one by one, as it is fetched into the server-side row cache. It becomes possible, then, that a lock which appeared to succeed when requested will nevertheless fail subsequently, when an attempt is made to fetch a row which becomes locked by another transaction.
The SELECT... WITH LOCK construct can succeed only in a top-level,
single-table SELECT statement. It is not available in a subquery specification, nor for joined sets. It cannot be specified with the DISTINCT operator, a GROUP BY clause or any other aggregating operation. It cannot be used in or with a view, nor with an external table, nor with the output of a selectable stored procedure.
*** For InterBase: ***
SELECT ... [FOR UPDATE [OF col [, col ...]]]
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Tue, 26 Aug 2003 6:46 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-09-03 19:51:29
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Wed, 3 Sep 2003 2:50 PM
Body:
Hi!
It seems as you already have the code for the dialect ;)
I could start following your instructions, but as I don't have an firebird installation currently available I would appreciate if you could you submit it as an patch ?
Please also answer if do not have it - then i'll have to do the "ground-work" ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Max Rydahl Andersen
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Sat, 30 Aug 2003 5:36 PM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-09-04 12:09:27
|
The following comment has been added to this issue:
Author: Reha CENANI
Created: Thu, 4 Sep 2003 7:09 AM
Body:
Ok, I will send patches for both dialects.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Max Rydahl Andersen
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Sat, 30 Aug 2003 5:36 PM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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...> - 2003-09-11 11:05:55
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 11 Sep 2003 6:04 AM
Body:
Where did you send those patches ? ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Max Rydahl Andersen
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Sat, 30 Aug 2003 5:36 PM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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
|
×
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