Hi Michael,
thanks for the prompt reply!
Unfortunately, refactoring the property "id" doesn't work either.
Refactoring from "id" to versionId" produces the following SQL from HQL:
Code:
main 18.01.2005 09:34:50.385 [DEBUG] net.sf.hibernate.hql.QueryTranslator SQL: select versionimp0_.versionId as versionId, versionimp0_.workspaceId as workspac2_, versionimp0_.ver_nr as ver_nr, versionimp0_.arb_lfdnr as arb_lfdnr, versionimp0_.ver_name as ver_name, versionimp0_.ver_ang_zeit as ver_ang_6_, versionimp0_.ver_loesch_jn as ver_loes7_, versionimp0_.ver_kommentar as ver_komm8_ from dbo.funver versionimp0_ where (versionimp0_.versionId=? )and(versionimp0_.workspaceId=? )
Please note that the java class' property names of the composite id as well as their coresponding db column names are built into the SQL. Is that behaviour correct? Sybase responds with the statement that it doesn't know any column "versionId" or "workspaceId" (the java properties which represents the coposite key).
When I run a coresponding HQL query for a class with no composite id the java property which represent the id is NOT built into the SQL.
Any ideas???
Very confused....
Cheers,
Oliver