• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Migrations and Prototypes Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Migrations and Prototypes Question


  • Subject: Re: Migrations and Prototypes Question
  • From: Tim Worman <email@hidden>
  • Date: Mon, 22 Oct 2018 12:09:05 -0700

Thanks Samuel,

I don’t have a working wolips dev environment either. It may not be worth it to
dig deeper. I’m still a little mystified though as to why none of the attribute
metadata from the model is available to the sychronization frameworks. I’m sure
there’s a great explanation but that seems like a huge gap.

T

> On Oct 21, 2018, at 12:05 PM, Samuel Pelletier <email@hidden> wrote:
>
> Hi Tim,
>
> I have the same problem with FrontBase and found where the code is but never
> tried to fix it.
>
> If I remember correctly, the code you are looking for is in the WOLips
> eclipse plugin in the EOModeler module. I do not think it would be really
> hard to fix but I do not have a working setup for WOLips development.
>
> Samuel
>
>
>> Le 19 oct. 2018 à 16:08, Tim Worman <email@hidden> a écrit :
>>
>> 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
>

 _______________________________________________
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

  • Follow-Ups:
    • AW: Migrations and Prototypes Question
      • From: Wolfgang Hartmann <email@hidden>
References: 
 >Migrations and Prototypes Question (From: Tim Worman <email@hidden>)
 >Re: Migrations and Prototypes Question (From: Samuel Pelletier <email@hidden>)

  • Prev by Date: Re: Migrations and Prototypes Question
  • Next by Date: Byte-range request
  • Previous by thread: Re: Migrations and Prototypes Question
  • Next by thread: AW: Migrations and Prototypes Question
  • Index(es):
    • Date
    • Thread