• 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: WO Equivalent of prepared statement
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO Equivalent of prepared statement


  • Subject: Re: WO Equivalent of prepared statement
  • From: Kieran Kelleher <email@hidden>
  • Date: Tue, 28 Oct 2008 10:45:03 -0400

Yeah ..... for single table logging apps. The *reason* EOF needs to generate and know about pks before saving is so that it can form the relationships before saving .... think to yourself how auto-increment could work in a multi-user environment where transactional saves are performed across many related tables, and you will understand that this "hassle" is a necessary thing ;-)

On Oct 28, 2008, at 9:23 AM, Randy Wigginton wrote:

Similarly in Mysql, creating a column as auto-increment can save all the "hassle" of generating a primary key.

_______________________________________________ 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: WO Equivalent of prepared statement
      • From: Ondřej Čada <email@hidden>
References: 
 >Re: WO Equivalent of prepared statement (From: "Cheong Hee (Datasonic)" <email@hidden>)
 >Re: WO Equivalent of prepared statement (From: Guido Neitzer <email@hidden>)
 >Re: WO Equivalent of prepared statement (From: Randy Wigginton <email@hidden>)

  • Prev by Date: intergrated EOModeler UI feature request
  • Next by Date: Re: intergrated EOModeler UI feature request
  • Previous by thread: Re: WO Equivalent of prepared statement
  • Next by thread: Re: WO Equivalent of prepared statement
  • Index(es):
    • Date
    • Thread