#1
  1. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Nov 2003
    Posts
    12
    Rep Power
    0

    PrimaryKey length


    Dear Friends,

    Primary columns length combinely should be less than or equal to 250 bytest in FireBird.

    Due to this the size of the column should be minimal. Can anybody know, this issue has got fixed in FireBird.

    regards,
    rajagopal
  2. #2
  3. Big Endian
    Devshed Beginner (1000 - 1499 posts)

    Join Date
    May 2001
    Location
    Fly-over country
    Posts
    1,172
    Rep Power
    30
    At the Firebird website, they list all the changes they make for each version. I could not find where this limitation has been changed:

    http://cvs.sourceforge.net/viewcvs.p...27&view=markup

    Fortunately this is an item that you can test yourself by creating a long primary key and seeing if it works with the version you're using. If it fails, you know the limitation still exists in your version.
  4. #3
  5. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Nov 2003
    Posts
    12
    Rep Power
    0

    Primary key length


    Actually I am using 1.0.3 Release version of FireBird. In this restriction for primary key column length is there. so i want to know whether the same is fixed in any later versions.

    regards,
    rajagopal
  6. #4
  7. Big Endian
    Devshed Beginner (1000 - 1499 posts)

    Join Date
    May 2001
    Location
    Fly-over country
    Posts
    1,172
    Rep Power
    30
    I could not find mention of this fix in Version 1.5 RC7.

    Version 1.5.0.3773 on my laptop would not let me create a 300 byte index.
  8. #5
  9. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Nov 2003
    Posts
    12
    Rep Power
    0
    Do u know any workaround for this
  10. #6
  11. Big Endian
    Devshed Beginner (1000 - 1499 posts)

    Join Date
    May 2001
    Location
    Fly-over country
    Posts
    1,172
    Rep Power
    30
    Use a surrogate key (a sequence number) instead of a natural key (a long multi-field key). This will allow you to relate one table to another. You still might have a problem if in order to maintain the integrity of your data you need to create a unique index on the natural key. You'll still run into that 250 byte limit.

IMN logo majestic logo threadwatch logo seochat tools logo