• 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: Reverse engineering with PostgreSQL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reverse engineering with PostgreSQL


  • Subject: Re: Reverse engineering with PostgreSQL
  • From: Paul Hoadley <email@hidden>
  • Date: Tue, 05 May 2015 17:23:50 +0930

On 5 May 2015, at 5:06 pm, Paul Hoadley <email@hidden> wrote:

> I presume there are some relevant differences between my converted database and a database generated from an EO Model, though I’m not sure what they are.  Does anyone have some experience with this?  What is the reverse engineering code looking for?  Are constraint _names_ magic, for example, because the converted database’s constraint names are slightly different to an EOF-generated database.  I’m happy enough to plod along with trial and error, but if someone knows what they’re doing, I’d love to get some tips.

Well, trial and error would suggest that the FK constraint names are not magic, but that column names _are_.  My conversion script (MS SQL → PostgreSQL) gave me column names of the form “bar” for a FK relationship to the “bar” table, rather than the more EOF-esque “bar_id”.  Even though the FK _constraint_ is present, the reverse engineering code seems to want to see a column name ending in “_id”.  For “bar” I get an integer attribute, for “bar_id” I get a relationship to Bar.  Trap for young players.


--
Paul Hoadley
http://logicsquad.net/



 _______________________________________________
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


References: 
 >Reverse engineering with PostgreSQL (From: Paul Hoadley <email@hidden>)

  • Prev by Date: Reverse engineering with PostgreSQL
  • Next by Date: Re: On SQL fully qualified names and how to implement them in EO,> model
  • Previous by thread: Reverse engineering with PostgreSQL
  • Next by thread: Re: On SQL fully qualified names and how to implement them in EO,> model
  • Index(es):
    • Date
    • Thread