• 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: Primary Key Maximum value
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Primary Key Maximum value


  • Subject: Re: Primary Key Maximum value
  • From: Guido Neitzer <email@hidden>
  • Date: Tue, 20 Mar 2007 13:56:24 -0600

On 20.03.2007, at 13:45, Mike Schrag wrote:

[FrontBase]
sql = "SELECT UNIQUE FROM " + quoteTableName (eoentity.primaryKeyRootName());

AFAIK: This will not return a long value, as "select unique" on FrontBase is limited to integer.


With PostgreSQL long keys work for me. PK generation is more or less different in nearly every setup (EO_PK_TABLE in OpenBase and MySQL, sequences in PostgreSQL, select unique in FrontBase, you name it).

So - if you need BIG keys, use either a database where the plugin (and the db of course) supports long keys, or use 24 byte binary keys from EOF.

cug
_______________________________________________
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: Primary Key Maximum value
      • From: Robert Walker <email@hidden>
References: 
 >Primary Key Maximum value (From: Miguel Arroz <email@hidden>)
 >Re: Primary Key Maximum value (From: Robert Walker <email@hidden>)
 >Re: Primary Key Maximum value (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Primary Key Maximum value
  • Next by Date: Re: Primary Key Maximum value
  • Previous by thread: Re: Primary Key Maximum value
  • Next by thread: Re: Primary Key Maximum value
  • Index(es):
    • Date
    • Thread