Hi Matt,
thank you for your hint. I'll have a closer look right now, shouldn't be
relatively easy to solve. I apologize for hastily applying the patch
without deeper inspection.
cherio
benjamin
Am 09.09.2011 22:30, schrieb Matt DeHoust (JIRA):
[
https://issues.apache.org/jira/browse/EMPIREDB-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt DeHoust reopened EMPIREDB-113:
-----------------------------------
Sorry I do not have time to submit a patch at the moment, but my original patch
only partially solves the problem. Consider a database column that is
DECIMAL(10,22), the patch yields an empire model size value of 12.2! So, you
expect DECIMAL(10,22) but get DECIMAL(12,2). I apologize for the hasty patch
that did not fully solve the problem.
Should preserve the decimal digits of DECIMAL columns
-----------------------------------------------------
Key: EMPIREDB-113
URL: https://issues.apache.org/jira/browse/EMPIREDB-113
Project: Empire-DB
Issue Type: Bug
Components: CodeGenerator
Affects Versions: empire-db-2.1.0-incubating
Reporter: Matt DeHoust
Assignee: Benjamin Venditti
Fix For: empire-db-2.2.0-incubating
Attachments: empire-db-codegen.patch.txt
The problem is that the codegen parser does not set the decimal digits for the
size of DECIMAL columns. This leads to problems if you use empire-db to
generate your schema. You expect DECIMAL(10,2) but get DECIMAL(10,0).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
