• 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
Some help with FrontBase and SQL generation (migrations mainly)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Some help with FrontBase and SQL generation (migrations mainly)


  • Subject: Some help with FrontBase and SQL generation (migrations mainly)
  • From: Ângelo Andrade Cirino <email@hidden>
  • Date: Mon, 04 May 2015 21:17:53 -0300

A common problem FrontBase users face with the current plug-in is the generated SQL for table creation containing malformed named constraints.

A quick and simple solution is to set USE_NAMED_CONSTRAINTS to false in the FrontBase plug-in source com.webobjects.jdbcadaptor._FrontBase

I submitted a pull request that helps with this (and much more), but the named constraints generated names are very long and not very useful. I needed to make them in a way to assure each named constraint name is really unique. Inheritance can cause naming conflicts when using the original name forming procedure and I had to make the names more complex, so less useful.

Angelo

Ângelo Andrade Cirino
email@hidden

"O homem sensato se adapta ao mundo. O insensato insiste em tentar adaptar o mundo a ele. Todo o progresso depende, portanto, do homem insensato"
Sir George Benard Shaw

"The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man."
Sir George Benard Shaw


 _______________________________________________
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

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