• 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: the trouble with migrations...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: the trouble with migrations...


  • Subject: Re: the trouble with migrations...
  • From: David Avendasora <email@hidden>
  • Date: Sat, 24 May 2014 12:00:58 -0400

Hi Tim,

In addition to the schema synchronization stuff you also need to look at the SQLHelper subclasses defined for the plug-in.

I believe these were created as part of Mike's original migrations implementation and it's entirely possible that there was never one created for open base and therefore it's not doing what it supposed.

Sorry I can't be more specific right now I'm not in front of my computer, but I've been digging around down in the plug-ins and the schema synchronization code quite a bit in the last couple months so I think I'll should be able to help more once I am back at my computer.  By Tuesday for sure.

Dave

Sent from my iPhone

> On May 23, 2014, at 7:26 PM, Timothy Worman <email@hidden> wrote:
>
> So, I’ve been looking into a problem with ERXMigrations related to OpenBase. The SQL in migrations is wonky which was detailed here many moons ago:
>
> http://prod.lists.apple.com/archives/webobjects-dev/2008/Oct/msg00431.html
>
> Namely, the “constraints” sql-isms are different. But wait, aren’t the frameworks supposed to build SQL expressions based on the JDBC plugin you’re using (in this case OpenBasePlugIn)?
>
> I decided to mess with the OpenBase plugin source and see if I could fix this issue - maybe sth more recent in WO-ness wasn’t being properly overridden in the plugin. This is what I’ve found -
>
> ERXMigrationDatabase.synchronizationFactory() is supposed to return a database-specific subclass of EOSynchronizationFactory (if I’m not mistaken). For OpenBase this should be OpenBaseSynchronizationFactory. However, it doesn’t appear to. The first time I run my app and ERAttachment0 is called, a standard base EOSynchronizationFactory (not OpenBaseSynchronizationFactory) is returned. No code from the subclass is called.
>
> Do others using PostgreSQL or other database experience this?
>
> Bueller…….Bueller……
>
> 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:
    • Re: the trouble with migrations...
      • From: Timothy Worman <email@hidden>
References: 
 >the trouble with migrations... (From: Timothy Worman <email@hidden>)

  • Prev by Date: Re: advice on inheritance??
  • Next by Date: Re: Any plans to build libapache2-mod-wo for Ubuntu 14.04 LTS
  • Previous by thread: the trouble with migrations...
  • Next by thread: Re: the trouble with migrations...
  • Index(es):
    • Date
    • Thread