Sensor tshift default value not allowed, not -999.00

[dimag1978]

When I read sensor css-table with tshift values equal to 0.0, they are written to the database as -999.0.
If I write the values from the database back to the file, the string length increases by one and is 140 characters, which is a bug.

[jkmacc-LANL]

@dimag1978 Thanks for opening. I'm looking into this, but it may be a little while before I can get into it. Do you have a minimum working example of the problem? Thanks again.

[dimag1978]

Thank you for your attention.
In my work I use Postrgresql 13 and data in CSS3.0 format.
With Pisces, I'm creating CSS3.0 database tables in a PostgreSQL database.
All data reads well (although I found a number of errors that I can write about as well).
As a client program for working with a PostgreSQL database, I use pgAdmin4, through which I view the created tables.
There was a problem with the Sensor table with the field - tshift.
In my file, the -tshift field is 0.00, which is the correct value. After loading into a PostgreSQL database, the tshift field becomes -999, which is an invalid value. After dumping the data from the PostgreSQL database back into a text file, the length of the string becomes longer. The dbe program (of the Antelope package) cannot open the created file and gives an error - the length of the line is wrong.