Bugzilla – Full Text Bug Listing
| Summary: | Handle database reserved keywords | ||
|---|---|---|---|
| Product: | [Modeling] EMFT | Reporter: | Mike Cooper <mcooper> |
| Component: | Texo | Assignee: | Martin Taal <mtaal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | Future | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
This has been solved, see the new property of the epackage annotation to encode sql reserved words. |
It would be nice if Texo somehow handled database reserved keywords. When switching from Teneo to Texo I hit a few reserved mysql keywords ("interval" and "key") I used for attribute names in my ecore model. These didn't show up as problems until runtime when I hit sql errors. Ideally Texo should somehow tell hibernate to map the attribute/property names to have a specific prefix for each db attribute name. i.e. stick "e_" or something before each variable name. If that's not possible, it would be nice if Texo at least warned about common reserved database keywords so these could be addressed at code gen time and not hidden until they are hit at runtime.