Migrations and Prototypes Question
Migrations and Prototypes Question
- Subject: Migrations and Prototypes Question
- From: Tim Worman <email@hidden>
- Date: Fri, 19 Oct 2018 13:08:37 -0700
I’ve got a conundrum and I’m hoping someone can help with it.
My model has some date value attributes defined in an entity (not timestamp).
In one case I’m using the ‘date’ prototype and in another I’m testing the
‘javaLocalDate’ prototype. When using these prototypes, all the value
conversions, etc., in the model are correct. They work. But I’ve always been
really flummoxed that migrations will never set the external fields as ‘date’
types in the target database.
So, I’ve been digging in to try and get to the bottom of it.
My databases (OpenBase and MySQL) both support ‘date’ types. In my Wonder
version, OpenBase and MySQL plugins support the more modern
EOSchemaSynchronizationFactory and in both cases the proper synchronization
factory is initialized when needed.
I’m overriding createTableStatementsForEntityGroup(NSArray entities)…
Good, I have entities here...but when I log out the entities (and attributes),
none of the metadata about the attributes’ prototypes, value conversions, etc.,
that appear in Entity Modeler are there - in other words I have no way to
capture the data type and override the external type that is being sent to the
database. When I log them out, all of the types are set to NSTimestamp.
Does anyone have any clues, tips, (or just hazard signs) that they can share
for why I’m finding this impossible?
Tim
UCLA GSE&IS
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden