[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3044?page=c...
]
Alexis Haumont commented on HHH-3044:
-------------------------------------
I was not refering to the default_schema property but to the schema attribute you can use
in the mapping.
Example : I have one main schema defined as my default_schema (say defaultSchema) but a
few entities I need to map are related to tables from another Sybase schema (say
otherSchema).
in one of my mapping file I will use :
< class name="Client" table="client"
schema="otherSchema" >
../..
wich will generate an sql query like :
select .. from fbi.client
Sybase syntax for schema is not 'fbi.client' but fbi..client (double point).
As a workaround I had to create many SQL views in my defaultScheam for each of theese
tables to have them accessible from within defaultSchema (hopefully theese entities were
readOnly for my application)..
Dialect.getSchemaSeparator() defined as char whereas sybase uses
'..' as schema delimiter
-----------------------------------------------------------------------------------------
Key: HHH-3044
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3044
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.0.5
Environment: Hibernate 3.0.5 used with Sybase ASE 12.5.4
Reporter: Alexis Haumont
Assignee: Gail Badner
With Sybase ASE, the naming pattern for schema indexes objects is :
schema..tableName
But the abstract class org.hibernate.dialect.Dialect has the following method signature
:
/**
* The separator between the schema/catalog/tablespace name and the table name.
*/
public char getSchemaSeparator() {
return '.';
}
It should be :
public String getSchemaSeparator() {
return ".";
}
and as such could ne overriden in SybaseDialect as :
public String getSchemaSeparator() {
return "..";
}
--
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