• 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: EO_PK_TABLE vs EO_SEQUENCE_TABLE
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE


  • Subject: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE
  • From: "Adam Chan" <email@hidden>
  • Date: Fri, 26 Sep 2003 11:06:35 -0600

We are running Sybase.

If I create a view and since it is a "read" only, will it likely cause a SQL
error when WebObjects tries to update the view table, or the update
statement on view will be ignored?


Hi Kaj,

Taking care the pk myself is sort of defeating the pupose of what WebObjects
made for. For every table that utilizes automatic pk generation, I will have
to write code that fetch/update the pk, that is just a whole lot of extra
work for both the developer and the machine.




----- Original Message -----
From: "Darryl Snover" <email@hidden>
To: <email@hidden>
Sent: Friday, September 26, 2003 9:46 AM
Subject: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE


> Well, you could likely create a view with the proper name.  Or, if on
> Oracle, use a Synonym....
>
> What database are you running against?
>
> -Best regards,
>
> Darryl Snover
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Using NSArray for Lists and WODisplayGroup for Batches (From: james o <email@hidden>)
 >EO_PK_TABLE vs EO_SEQUENCE_TABLE (From: "Adam Chan" <email@hidden>)
 >Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE (From: Darryl Snover <email@hidden>)

  • Prev by Date: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE
  • Next by Date: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE
  • Previous by thread: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE
  • Next by thread: Re: EO_PK_TABLE vs EO_SEQUENCE_TABLE
  • Index(es):
    • Date
    • Thread