Tersus: Re: I dont know what happened with new created Tables

Re: I dont know what happened with new created Tables Date: Aug 28, 2010The NULL issue (in the first screenshot) is a result of the way Tersus creates database schema. Namely:

When a table is created, which occurs the first time the server is accessed after the Database Record element has been added to the model, if no field is explicitly defined as primary key (i.e. no data element in the database record has the primarkKey property set to true), then the first field in the database is set as the primary key, and therefore cannot be set to NULL.

When the table schema is updated, as a result of changes in the Database Record model, only certain changes are reflected in the database, specifically, new fields are added, but deleted/renamed fields are not removed, and changes to primaryKey property are not applied.

It looks like you created myTable twice. First it included an ID field (which was the initial primary key), and then you removed the myTable definition and created it again, this time without an ID primary key, but since the myTable was already defined in the database, the ID column definition remained.The second issue is due to the fact that you named one of the fields POSITION, which is reserved in the sql dialect of hsqldb (the database server embedded in the studio).Regards,DavidSee Also:

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...