Issue 80 in sarasvati: "Invalid column name 'behaviour'" or similar error in case-sensitive databases

[sara...@googlecode.com]

Status: New
Owner: ----

New issue 80 by vaverche...@appsecinc.com: "Invalid column
name 'behaviour'" or similar error in case-sensitive databases
http://code.google.com/p/sarasvati/issues/detail?id=80

What steps will reproduce the problem?
Try to run Sarasvati with HibEngine on case-sensitive database; it will
complain about 'behaviour' column.

What version of the product are you using? On what operating system?
Version: Sarasvati 2.0.1, Windows

Please provide any additional information below.
HibNodeType class defines column name in wf_node_type as 'Behaviour',
while HibNode class refers to this column as 'behaviour' in the
@DiscriminatorFormula.

Problem may be fixed by
- changing column name to 'Behaviour' in the HibNode statement (see
attached patch),
- or changing column name to 'behaviour' in HibNodeType and schema.

The first fix is preferable - to keep compatibility with existing database
schemas.





Attachments:
case-sensititivity.patch 699 bytes

[sara...@googlecode.com]

Updates:
Status: Fixed

Comment #1 on issue 80 by plor...@gmail.com: "Invalid column

name 'behaviour'" or similar error in case-sensitive databases
http://code.google.com/p/sarasvati/issues/detail?id=80

This issue was closed by revision r1282.

[sara...@googlecode.com]

Updates:
Owner: plor...@gmail.com
Labels: Type-Defect Language-java Milestone-2.0.2 Usability
Component-Core-Hib OpSys-All

Comment #2 on issue 80 by plor...@gmail.com: "Invalid column

name 'behaviour'" or similar error in case-sensitive databases
http://code.google.com/p/sarasvati/issues/detail?id=80

Thank you for submitting this.

I went with changing the @JoinColumn attribute. Either change would cause
backwards incompatibility depending on if the DB was created using
hibernate or the scripts (since the scripts have the correct casing). Since
it was a lose-lose situation, I figured I should go with the change that
preserves consistency with the rest of the codebase.

[sara...@googlecode.com]

Comment #3 on issue 80 by plor...@gmail.com: "Invalid column

name 'behaviour'" or similar error in case-sensitive databases
http://code.google.com/p/sarasvati/issues/detail?id=80

If this fix is useful to you, I can cut a 2.0.2 release. Otherwise, I'll
wait a bit and see if any other bug reports come in the next couple of
weeks.

[sara...@googlecode.com]

Comment #4 on issue 80 by vaverche...@appsecinc.com: "Invalid column

name 'behaviour'" or similar error in case-sensitive databases
http://code.google.com/p/sarasvati/issues/detail?id=80

Thank you Paul,

I can wait till the next release - if you plan it within 2 month