Whenever I try to choose a data type for any column I get this message. I don't type by myself but choose from drop-down menu instead.
Details message as follows,
Error setting property 'dataType' value
Bad data type name specified: serial
it can be any type instead of serial, the result message will be the same.
The database is PostgreSQL.
Same problem :(
Dbeaver 5.2.5, Fedora 29, PostgreSQL 9.6
Related
"SERIAL" type does not exist yet, so how can we do the basic auto increment field in DBeaver 21.O via his GUI ?
You can set "serial" as data type with DBeaver GUI
serialViaDBeaver
And why serial type does not exist yet? I can see it in documentation
I am trying to push data from PG-12 to Clickhouse via FDW extension ("clickhouse_fdw") and it gives me error:
SQL Error [HV004]: ERROR: cannot convert constant value to clickhouse
value Hint: Constant value data type: 2950
Sherlocking gave me error in uuid, excepting this field passes on to data transfer. If I cast it to text it gives error, that target field is uuid not text. I am confused. Which data type casting is appropriate here? Please advise DB gurus :) Thanks beforehands.
I am using DB2 9.7 (LUW) in a windows server, in which multiple DBs are available in a single DB instance. I just found that in one of these DBs, I am unable to add a column with DATE data type, during table creation or altering. The column been added is getting changed to timestamp instead.
Any help on this will be welcome.
Check out your Oracle Compatibility setting
Depending on that setting a date is interpreted as Timestamp(0) like in your example.
Because these settings take effect if the database has been created after setting the DB2_COMPATIBILITY_VECTOR registry variable your database can show a different behaviour.
Symmetricds server is configured with postgresql 9.4 and client nodes have sqlite3. I recently had to alter a table at the server end and then send the schema to the client with the command symadmin send-schema --engine <server> --node <node> <table>
One of the changes in the table was the addition of default value on date field update_date date DEFAULT ('now'::text)::date
Since the changes is applied, on symmetric log I am seeing the following error message on the server side now:
ERROR [<server>] [AcknowledgeService] [qtp1874154700-1322] The outgoing batch <node>-41837 failed. ERROR: invalid input syntax for type date: "'now'::text)::date"
Is this error showing up because sqlite3 does not support 'now'::text)::date" as default value? In such case how can I propagate the changes?
OR
If it is a symmetricds issue that it is not recognizing 'now'::text)::date" as default value for update_date field?
I am suspecting due to this error all the synchronization between client and server is stopping.
Any clue is appreciated.
hope the problem is not in production
you'll need to delete the outgoing batch with the change or just the link between it and the alter table
use the command line then to send the custom native SQL DDL statement to each node from the central node or do it manually connecting remotely to each node
A batch in error will hold up all other batches in error. You can ignore the batch in error by setting the status to "IG" on that particular batch. However this would result in all change captures in the batch to not be applied on the target.
Are you sure the default value applied correctly on SQLITE. Here is an example of a table with a default date value of now.
create table forum (id int primary key, some_date date default(date('now')));
You can then send the appropriate alters or creates to your clients through the send sql feature.
References:
Open source send documentation.
Professional send documentation.
I'm trying to implement the Simple Avatar Uploader on my User domain class but I seem to have encountered a conflicting issue with grails implementation of byte[] and PostgreSQL. I have implemented it exactly as the plugin page suggests but on compilation I get the error:
Error: Error executing SQL ALTER TABLE user ADD avatar bytea(16384): ERROR: type modifier is not allowed for type "bytea"
I have found some help suggesting that PostgreSQL does not accept a size modifier but removing the maxSize: 16384 constraint only leads to the exact same error with a different size:
Error: Error executing SQL ALTER TABLE user ADD avatar bytea(255): ERROR: type modifier is not allowed for type "bytea"
So it seems that grails will automatically set the size to 255 if no maxSize is provided. Is there a way to override this? Or perhaps a more suitable data type for byte arrays?
Thanks!
Not sure if it was directly responsible or not but we are using Grails Database Migration and we solved the issue by editing the latest migration script changing the line
column(name: "avatar", type: "bytea(255)")
to
column(name: "avatar", type: "bytea")