Issue Details (XML | Word | Printable)

Key: NUCJPA-28
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
DataNucleus API JPA

Support JPA "columnDefinition" at least in a minimal way

Created: 19/May/09 10:47 AM   Updated: 11/Sep/09 08:42 AM   Resolved: 19/May/09 11:09 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.4, 2.0.0.m1


 Description  « Hide
The JPA unspecified "columnDefinition" is a retarded idea allowing users to put any old crap into the definition of a column, and expect the implementation to just pass it through to the datastore in schema generation. It doesn't define *what* can be put in there and what not. We should support it only as something that is *appended* to the definition we provide ourselves by other means.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 19/May/09 11:09 AM
User-entered string is *appended* to the column definition that DataNucleus generates itself. So if we think it will be NOT NULL then we create "{colName} {colType} NOT NULL" and any user-supplied stuff is after that. Not sure I see the point, but then it is JPA