kmmbvnr / sarasvati

Automatically exported from code.google.com/p/sarasvati
0 stars 5 forks source link

"Invalid column name 'behaviour'" or similar error in case-sensitive databases #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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.

Original issue reported on code.google.com by vaverche...@appsecinc.com on 23 Jan 2013 at 9:18

Attachments:

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1282.

Original comment by plor...@gmail.com on 27 Jan 2013 at 5:44

GoogleCodeExporter commented 9 years ago
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.

Original comment by plor...@gmail.com on 27 Jan 2013 at 5:47

GoogleCodeExporter commented 9 years ago
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.

Original comment by plor...@gmail.com on 27 Jan 2013 at 5:49

GoogleCodeExporter commented 9 years ago
Thank you Paul,

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

Original comment by vaverche...@appsecinc.com on 29 Jan 2013 at 3:39

GoogleCodeExporter commented 9 years ago
Released with v2.0.2

Original comment by plor...@gmail.com on 3 Mar 2013 at 2:59