Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

First let me state this answer will not deal with UUID of any sort. Not set to deal with so will talk here of SMALLSERIAL, SERIAL and BIGSERIAL.

It appears the bug report you refer to is only discussing the creation of an auto increment field when creating/editing a table through Base and not its' generated values when entering data.

Have been using SERIAL now for about 6 to 9 months on a regular basis without problems. Have just tested SMALLSERIAL and BIGSERIAL and each appear to work correctly with a caveat not in SERIAL. This is the display of the value generated as records are entered:

image description

Bottom left is table definition. Table was actually created using pgAdmin3. SQL used was simple:

CREATE TABLE vegies(
   id SMALLSERIAL PRIMARY KEY,
   name VARCHAR NOT NULL
);

Top left is a newly entered record. Notice the id is 0. With that, opened a different form on bottom right and it shows the correct id for the 'squash' entry. Top right is a table view with 'squash' entry correct & newly entered 'onion' record and again id = 0. Each of the three views were opened without modification to the prior to show the problem. That is the actual id value is not known until the current view is closed & re-opened or a new view is opened.

Also, when editing a table, even though set as auto value, only SERIAL displays this in Base:

image description

Can't say this is a problem or not since this field need not even be present on a form for the form to work.

Hello,

First let me state this answer will not deal with UUID of any sort. Not set to deal with so will talk here of SMALLSERIAL, SERIAL and BIGSERIAL.

It appears the bug report you refer to is only discussing the creation of an auto increment field when creating/editing a table through Base and not its' generated values when entering data.

Have been using SERIAL now for about 6 to 9 months on a regular basis without problems. Have just tested SMALLSERIAL and BIGSERIAL and each appear to work correctly with a caveat not in SERIAL. This is the display of the value generated as records are entered:

image description

Bottom left is table definition. Table was actually created using pgAdmin3. SQL used was simple:

CREATE TABLE vegies(
   id SMALLSERIAL PRIMARY KEY,
   name VARCHAR NOT NULL
);

Top left is a newly entered record. Notice the id is 0. With that, opened a different form on bottom right and it shows the correct id for the 'squash' entry. Top right is a table view with 'squash' entry correct & newly entered 'onion' record and again id = 0. Each of the three views were opened without modification to the prior to show the problem. That is the actual id value is not known until the current view is closed & re-opened or a new view is opened.

Also, when editing a table, even though set as auto value, only SERIAL displays this in Base:

image description

Can't say this is a problem or not since this field need not even be present on a form for the form to work.

EDIT:

After posting this, completely shut down the Base files & pgAdmin3. Then re-opened the Base file & all problems regarding id=0 have gone away. Correct auto id is showing in all three types.