You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, NHibernate can have the identical bug but leave it unfixed.
The text was updated successfully, but these errors were encountered:
fredericDelaporte
changed the title
Oracle8iDialect may not name tempory tables HT_ prefix
Oracle8iDialect may not name tempory tables with HT_ prefix
Dec 24, 2023
fredericDelaporte
changed the title
Oracle8iDialect may not name tempory tables with HT_ prefix
Oracle8iDialect may not name temporary tables with HT_ prefix
Dec 24, 2023
Excepted the name discrepancy for some tables, has this bug any other effect? (Does the HT_ or T_ prefix has any special treatment with Oracle? Looking at the documentation, is does not seem so.)
The possible breaking change for this change is in case the database already has some other table with a name which would match the renamed temporary table: it may cause a name conflict that was previously avoided through the bug.
Oracle8iDialect may not name all temporary tables with HT_ prefix. Some may be prefixed with T_ instead.
This bug was reported to hibernate:
https://hibernate.atlassian.net/browse/HHH-9290
The buggy code of hibernate is as follows:
The fixed code is as follows:
The latest NHibernate is identical to the buggy code:
As a result, NHibernate can have the identical bug but leave it unfixed.
The text was updated successfully, but these errors were encountered: