(Not Signed In)

Sign In

.NET Development: Transactional Repositories - Undocumented "id" field in tables

Bottom of Page

1 to 4 of 4

  1.  
    • CommentAuthorDavid K
    • CommentTimeMar 31st 2010
     
    It has been discovered that a field named "id" is added by GeoBase to every table upon creation. Can this field name be modified through config files? It appears this field is not documented. Are there other fields that are added by default?
    •  
      CommentAuthorPepitaL
    • CommentTimeApr 5th 2010
     
    David,

    There are no other field created by default.
    The "id" is a unique identifier within the table for each row of the table.
    This field cannot be modified.
    A ticket has been logged to get the "id" field referenced in the documentation

    Pepita
    • CommentAuthorwpearse
    • CommentTimeApr 8th 2010
     
    Hey David,

    I'm curious as to what you're using the Transactional Repos for?

    I've always used a transactional repo as a one-shot datastore that persists only while my app is running. Each time my app is launched I overwrite the old database and create a new one.

    Pepita is right in saying that the 'id' field is unique and can't be set. I don't understand why you would want to change this though... if you need a unique ID that you can set, is it worth creating a new 'uid' or something field for your table?

    Cheers,
    Will
    • CommentAuthorDavid K
    • CommentTimeApr 12th 2010
     
    Will,
    We were looking at the transactional repos as a method for storing persistent data, not just data available during a single run of an application. In fact, what led us to discover this is we were importing data from a CSV file with a column named ID and it collided with the id column created by geobase (note the case insensitivity on the column names).

    David.

1 to 4 of 4

  1.