Can not edit column names

[Tom]

Hi, I have a problem with editing my column names.
It is not editable. Why is that?

Thanks.

[Tom]

Another error. I created the sudents table with sql statement.

Code: Select all

CREATE TABLE sekit.students
(
id INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1),
name VARCHAR(24) NOT NULL,
address VARCHAR(1024),
CONSTRAINT primary_key PRIMARY KEY (id)
) ;


It works, the problem is that it places default value as autoincrement instead of checking the check box. So if I create a table within dbSchema I cant add auto increment property.To do so I have to add this STRING"AUTOINCREMENT: start 1 increment 1" as default value of the column, but i does not allow me because it expect an INTEGER value.

[donose.mihai]

Hi, I have a problem with editing my column names.
It is not editable. Why is that?

Thanks.

Hi Tom,

Dbschema executes an alter table in the background when you change a table name, it look like this statement either was not implemented or it has an error in it, we'll solve it in our next update, thanks for letting us know about it.

[donose.mihai]

Another error. I created the sudents table with sql statement.

Code: Select all

CREATE TABLE sekit.students
(
id INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1),
name VARCHAR(24) NOT NULL,
address VARCHAR(1024),
CONSTRAINT primary_key PRIMARY KEY (id)
) ;


It works, the problem is that it places default value as autoincrement instead of checking the check box. So if I create a table within dbSchema I cant add auto increment property.To do so I have to add this STRING"AUTOINCREMENT: start 1 increment 1" as default value of the column, but i does not allow me because it expect an INTEGER value.

Noted, it will be solved in the next update.

[firionicable]

Hi Tom,

Dbschema executes an alter table in the background when you change a table name, it look like this statement either was not implemented or it has an error in it, we'll solve it in our next update, thanks for letting us know about it.

Nice. I can finally use DBschema again once I get the latest version where this problem has been fixed. Thanks.