[jira] [Commented] (EMPIREDB-217) Consistency check for data model defintion vs deployed data model

2015-05-13 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541930#comment-14541930 ] jan commented on EMPIREDB-217: -- Hello Rainer, I made a pullrequest on GitHub (nice to see

[jira] [Commented] (EMPIREDB-217) Consistency check for data model defintion vs deployed data model

2015-04-12 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491940#comment-14491940 ] jan commented on EMPIREDB-217: -- Hi Rainer, here is a second version. I fixed a small bug

[jira] [Created] (EMPIREDB-231) Improve CheckboxInputControl

2015-09-30 Thread jan (JIRA)
jan created EMPIREDB-231: Summary: Improve CheckboxInputControl Key: EMPIREDB-231 URL: https://issues.apache.org/jira/browse/EMPIREDB-231 Project: Empire-DB Issue Type: Improvement

[jira] [Reopened] (EMPIREDB-184) DBCompareColExpr does not properly escape characters when generating SQL

2016-08-01 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan reopened EMPIREDB-184: -- My initial fix breaks escaping for String with ' > DBCompareColExpr does not properly escape characters when

[jira] [Resolved] (EMPIREDB-184) DBCompareColExpr does not properly escape characters when generating SQL

2016-08-01 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-184. -- Resolution: Fixed Fixed in commit e769f0f8600f815b6d3848ab06dfc103fa4bd15d > DBCompareColExpr does not

[jira] [Created] (EMPIREDB-246) Label Required Mark check inconsistent

2016-07-21 Thread jan (JIRA)
jan created EMPIREDB-246: Summary: Label Required Mark check inconsistent Key: EMPIREDB-246 URL: https://issues.apache.org/jira/browse/EMPIREDB-246 Project: Empire-DB Issue Type: Bug

[jira] [Resolved] (EMPIREDB-245) Add Supprt for DELETE with JOIN for MySQL

2016-07-21 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-245. -- Resolution: Fixed Added in commit

[jira] [Created] (EMPIREDB-245) Add Supprt for DELETE with JOIN for MySQL

2016-07-21 Thread jan (JIRA)
jan created EMPIREDB-245: Summary: Add Supprt for DELETE with JOIN for MySQL Key: EMPIREDB-245 URL: https://issues.apache.org/jira/browse/EMPIREDB-245 Project: Empire-DB Issue Type: Improvement

[jira] [Updated] (EMPIREDB-247) Add Support for "insertOrUpdate" ("UPSERT")

2016-08-08 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-247: - Description: It should be possible to create a "insertOrUpdate" statement from a DBCommand and perform a

[jira] [Created] (EMPIREDB-247) Add Support for "insertOrUpdate" ("UPSERT")

2016-08-08 Thread jan (JIRA)
jan created EMPIREDB-247: Summary: Add Support for "insertOrUpdate" ("UPSERT") Key: EMPIREDB-247 URL: https://issues.apache.org/jira/browse/EMPIREDB-247 Project: Empire-DB Issue Type: Improvement

[jira] [Assigned] (EMPIREDB-184) DBCompareColExpr does not properly escape characters when generating SQL

2016-07-22 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan reassigned EMPIREDB-184: Assignee: jan > DBCompareColExpr does not properly escape characters when generating SQL >

[jira] [Created] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2016-11-17 Thread jan (JIRA)
jan created EMPIREDB-249: Summary: Add "format" Support to MySQL convert expression Key: EMPIREDB-249 URL: https://issues.apache.org/jira/browse/EMPIREDB-249 Project: Empire-DB Issue Type:

[jira] [Resolved] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2016-11-17 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-249. -- Resolution: Fixed I added case TEXT: if (format != null) { //

[jira] [Reopened] (EMPIREDB-184) DBCompareColExpr does not properly escape characters when generating SQL

2016-12-12 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan reopened EMPIREDB-184: -- The initial solution did not work if you had \ AND ' > DBCompareColExpr does not properly escape characters when

[jira] [Updated] (EMPIREDB-184) DBCompareColExpr does not properly escape characters when generating SQL

2016-12-12 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-184: - Fix Version/s: (was: empire-db-2.4.5) empire-db-2.4.6 > DBCompareColExpr does not

[jira] [Created] (EMPIREDB-252) Add Support for database specific CodeGenParser

2016-12-02 Thread jan (JIRA)
jan created EMPIREDB-252: Summary: Add Support for database specific CodeGenParser Key: EMPIREDB-252 URL: https://issues.apache.org/jira/browse/EMPIREDB-252 Project: Empire-DB Issue Type:

[jira] [Resolved] (EMPIREDB-252) Add Support for database specific CodeGenParser

2016-12-02 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-252. -- Resolution: Fixed I added the protected method getColumnSize in CodeGenParser which behaves like the

[jira] [Created] (EMPIREDB-250) DBDDLGenerator generates wrong SQL for Views with DBCombinedCmd

2016-11-30 Thread jan (JIRA)
jan created EMPIREDB-250: Summary: DBDDLGenerator generates wrong SQL for Views with DBCombinedCmd Key: EMPIREDB-250 URL: https://issues.apache.org/jira/browse/EMPIREDB-250 Project: Empire-DB Issue

[jira] [Created] (EMPIREDB-251) Add Support for TINYINT, MEDIUMINT Integer Types for MySQL

2016-12-01 Thread jan (JIRA)
jan created EMPIREDB-251: Summary: Add Support for TINYINT, MEDIUMINT Integer Types for MySQL Key: EMPIREDB-251 URL: https://issues.apache.org/jira/browse/EMPIREDB-251 Project: Empire-DB Issue Type:

[jira] [Resolved] (EMPIREDB-251) Add Support for TINYINT, MEDIUMINT Integer Types for MySQL

2016-12-01 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-251. -- Resolution: Fixed Added in commit 9a45804cefb27c7628451532c1514d51d622da2f > Add Support for TINYINT,

[jira] [Created] (EMPIREDB-261) DBCommand is not re-usable, when a CLOB colum is involved

2017-07-12 Thread jan (JIRA)
jan created EMPIREDB-261: Summary: DBCommand is not re-usable, when a CLOB colum is involved Key: EMPIREDB-261 URL: https://issues.apache.org/jira/browse/EMPIREDB-261 Project: Empire-DB Issue Type:

[jira] [Updated] (EMPIREDB-261) DBCommand is not re-usable, when a CLOB colum is involved

2017-07-12 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-261: - Description: When you write code like this: cmd.set(DB.col1.to(col1)); cmd.set(DB.col2.to(col2)); // ...

[jira] [Created] (EMPIREDB-264) MySQL Driver: Update Keywords for version 5.7

2017-10-13 Thread jan (JIRA)
jan created EMPIREDB-264: Summary: MySQL Driver: Update Keywords for version 5.7 Key: EMPIREDB-264 URL: https://issues.apache.org/jira/browse/EMPIREDB-264 Project: Empire-DB Issue Type: Improvement

[jira] [Resolved] (EMPIREDB-264) MySQL Driver: Update Keywords for version 5.7

2017-10-13 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-264. -- Resolution: Fixed > MySQL Driver: Update Keywords for version 5.7 >

[jira] [Resolved] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2017-10-09 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-249. -- Resolution: Fixed > Add "format" Support to MySQL convert expression >

[jira] [Commented] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2017-10-09 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196669#comment-16196669 ] jan commented on EMPIREDB-249: -- Looks like noone every used it. Fixed in commit

[jira] [Reopened] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2017-10-09 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan reopened EMPIREDB-249: -- This fix added a new bug: convertig to TEXT without format default to converting to BLOB > Add "format" Support

[jira] [Updated] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2017-10-09 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-249: - Fix Version/s: (was: empire-db-2.4.6) empire-db-2.4.7 > Add "format" Support to MySQL

[jira] [Updated] (EMPIREDB-249) Add "format" Support to MySQL convert expression

2017-10-09 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-249: - Affects Version/s: empire-db-2.4.6 > Add "format" Support to MySQL convert expression >

[jira] [Commented] (EMPIREDB-269) DBDatabaseDriverPostgreSQL: wrong SQLPhrase for DBSystemDate

2018-01-15 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325976#comment-16325976 ] jan commented on EMPIREDB-269: -- {code:java} postgres=# SELECT CURRENT_DATE(); ERROR: syntax error at or

[jira] [Resolved] (EMPIREDB-269) DBDatabaseDriverPostgreSQL: wrong SQLPhrase for DBSystemDate

2018-01-15 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan resolved EMPIREDB-269. -- Resolution: Fixed fixed in commit 4f02a5d9909615760f1b01efa5521326d0193181 > DBDatabaseDriverPostgreSQL:

[jira] [Created] (EMPIREDB-281) SelectInputControl: Problem with updating options

2018-10-30 Thread jan (JIRA)
jan created EMPIREDB-281: Summary: SelectInputControl: Problem with updating options Key: EMPIREDB-281 URL: https://issues.apache.org/jira/browse/EMPIREDB-281 Project: Empire-DB Issue Type: Bug

[jira] [Comment Edited] (EMPIREDB-283) PreparedStatements not working with MS SQL-Server > 2012

2019-01-17 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744782#comment-16744782 ] jan edited comment on EMPIREDB-283 at 1/17/19 8:27 AM: --- [~doebele]: I just had a

[jira] [Commented] (EMPIREDB-283) PreparedStatements not working with MS SQL-Server > 2012

2019-01-17 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744782#comment-16744782 ] jan commented on EMPIREDB-283: -- [~doebele] I just had a look at the dumps and did a test-restore. My

[jira] [Commented] (EMPIREDB-283) PreparedStatements not working with MS SQL-Server > 2012

2019-01-16 Thread jan (JIRA)
[ https://issues.apache.org/jira/browse/EMPIREDB-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744711#comment-16744711 ] jan commented on EMPIREDB-283: -- [~doebele]: I had / have the same (or a similar) problem with Postgres.