I am running a script to populate a table on an SQL Server 2017 database using SQLAlchamy. The script ran flawlessly a few weeks ago.
Essentially, the server does not seem to be populating default values on on non nullable fields.
For example, when I run the following statement (as rendered by SQLA):
INSERT INTO concept
(
retired,
short_name,
description,
form_text,
datatype_id,
class_id,
is_set,
creator,
date_created,
version,
changed_by,
date_changed,
retired_by,
date_retired,
retire_reason,
uuid,
note_regex
)
VALUES
(
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?
)'] [parameters: (0,
'ck',
'creatine phosphokinase',
None,
14,
49,
0,
0,
None,
None,
None,
None,
None,
None,
None,
'cf6443ff-f2a1-49ab-96e3-c5d6fac362ed', None)]
I receive the error:
Cannot insert the value NULL into column 'date_created',
table 'myositis_longetudinal_cohort.dbo.concept'; column does not allow
nulls. INSERT fails. (515)
This is confusing to me since the the date_created field has a default value of getdate()
Here is the constraint statement:
ALTER TABLE [dbo].[concept]
ADD CONSTRAINT [DF__concept__date_cr__62AFA012] DEFAULT (Getdate()) FOR
[date_created]
I am new to SQL Server and am not sure what I may be missing. The server was update on 11/15/18, but I did not see anything in the update that could explain the change.
Thanks in advance for any help!
INSERT INTO concept
(
retired,
short_name,
description,
form_text,
datatype_id,
class_id,
is_set,
creator,
date_created, <--SPECIFYING HERE MEANS DEFAULT WON'T BE USED
version,
changed_by,
date_changed,
retired_by,
date_retired,
retire_reason,
uuid,
note_regex
)
And the parameters:
[parameters: (
0, <-- retired,
'ck', <-- short_name,
'creatine phosphokinase', <-- description,
None, <-- form_text,
14, <-- datatype_id,
49, <-- class_id,
0, <-- is_set,
0, <-- creator,
None, <-- date_created (provided with NULL)
None,
None,
None,
None,
None,
None,
'cf6443ff-f2a1-49ab-96e3-c5d6fac362ed',
None
)]
The same problem will occur for any other columns in your table that have a NON_NULL_DEFAULT+NOTNULL_CONSTRAINT
As to possibilities why it's suddenly started happening:
SQLAlchemy never used to generate an insert that specified this column
The NOT NULL constraint was added
A trigger supplying values in the case of a null being passed has been removed, re-coded or disabled
Thanks to everyone.
It turns out, that it was an SQLAlchemy issue.
I had to add autoload: true to my __table_args__ instead of manually defining each Column. Apparently, If you do not allow SQLA to introspect the table, it will pass NULL as a value instead of skipping the value when generating the insert statement as suggested by #larnu and others.
Related
I have a JDBC application that uses postgres INSERT INTO / ON CONFLICT to perform an upsert query. We would like to support H2 as well, but H2 uses the MERGE query instead. How would I go about translating the following query into H2's syntax? The H2 code will be in a separate library, which means that it doesn't have to work in both postgres and H2.
INSERT INTO dest_table(id,
field1,
field2,
field3,
field4)
VALUES (?, ?, ?, ?, ?)
on conflict (id) do update
set (field3,field3) = (excluded.field3, excluded.field4)
Of course, as soon as I posted to StackOverflow I figured it out. Here is my solution:
Table setup
drop table if exists characters;
CREATE TABLE characters (
id int not null,
first character varying(50),
last character varying(50));
insert into characters (id, first, last) values ( 1, 'scooby', 'doo' );
insert into characters (id, first, last) values ( 2, 'eric', 'cartman' );
insert into characters (id, first, last) values ( 3, 'luke', 'skywalker' );
select * from characters;
-------------------------
1,scooby,doo
2,eric,cartman
3,luke,skywalker
The update query looks like this (with hardcoded values, but it should work with placeholders as well)
Insert (no conflict):
merge into characters
using values (4, 'darth', 'vader') as incoming(id,first,last)
on characters.id = incoming.id
when not matched then
insert (id, first, last) values (incoming.id, incoming.first, incoming.last)
when matched then
update set first = incoming.first, last = incoming.last;
select * from characters;
-------------------------
1,scooby,doo
2,eric,cartman
3,luke,skywalker
4,darth,vader
Update (conflict on 'id', just updates darth vader to anikan skywalker):
merge into characters
using values (4, 'anikan', 'skywalker') as incoming(id,first,last)
on characters.id = incoming.id
when not matched then
insert (id, first, last) values (incoming.id, incoming.first, incoming.last)
when matched then
update set first = incoming.first, last = incoming.last;
select * from characters;
-------------------------
1,scooby,doo
2,eric,cartman
3,luke,skywalker
4,anikan,skywalker
I'm trying to do the following using expo-sqlite in react-native:
tx.executeSql(`
INSERT INTO composers (
lastName,
firstName,
birthDate,
deathDate
) VALUES (?, ?, ?, ?);
ON CONFLICT(lastName, firstName, birthDate, deathDate) DO
UPDATE SET
lastName = excluded.lastName,
firstName = excluded.firstName,
birthDate = excluded.birthDate,
deathDate = excluded.deathDate
`,
[
composer.lastName,
composer.firstName,
composer.birthDate,
composer.deathDate
], (_, resultSet) => {
//console.log(JSON.stringify(rows));
const insertId = resultSet.insertId ? resultSet.insertId : 0;
console.log("INSRTED COMPOSER")
console.log(insertId)
},
(tx, error) => dbErrorCallback(tx, error)
);
I have a UNIQUE(lastName, firstName, birthDate, deathDate) constraint on the composers table, and I'm getting an error that the unique constraint failed when I'm inserting a composer who already exists. I'm expecting it to move on to the ON CONFLICT DO UPDATE SET part, but it seems like it doesn't, I'm not even getting to the console.log("INSRTED COMPOSER") part.
I tried removing the semicolon after the VALUES (?, ?, ?, ?); part, but then I get a syntax error.
What I'm basically trying to do overall is to insert a composer and then use the row id to get the autoincremented primary key of the composer to do more inserts, OR if the composer already exists, get its primary key to do more inserts. But I can't even get this first part working.
I'm trying to insert a flowfile from NiFi into PostgreSQL database. Flowfile is a JSON which keys are: id, timestamp, metric1, metric2, ..., and I have problems with timestamp data.
This is the value of SQL Insert statement:
INSERT INTO egillor.metrics (id, consumo_red, generacion_pv, timestamp) VALUES (?, ?, ?, ?)
And this is the error
Unable to execute SQL select query INSERT INTO egillor.metrics (id, consumo_red, generacion_pv, timestamp)
VALUES (?, ?, ?, ?) for StandardFlowFileRecord ... due to
java.sql.SQLDataException: The value of the sql.args.4.value is '2021-05-22T00:00:00+02:00', which cannot
be converted to a timestamp; routing to failure:
At the middle of the log, I have the following clue, but I don't now how to fix it
Caused by: java.text.ParseException: Unparseable date: "2021-05-22T00:00:00+02:00"
So, I have to deal with java.text.ParseException from inside a PutDatabaseRecord processor...
Does anyone had this problem in the past? Does anyone know how I can fix it?
I'm mediocre with perl and new to SQL, so excuse any lameness.
I've got a perl script I'm working on that interacts with a database to keep track of users on IRC. From tutorials I've found, I've been able to create the db, create a table within, INSERT a new record, UPDATE a field in that record, and SELECT/find records based on a field.
The problem is, I can only figure out how to UPDATE one field at a time and that seems inefficient.
The code to create the table:
my $sql = <<'END_SQL';
CREATE TABLE seenDB (
id INTEGER PRIMARY KEY,
date VARCHAR(10),
time VARCHAR(8),
nick VARCHAR(30) UNIQUE NOT NULL,
rawnick VARCHAR(100),
channel VARCHAR(32),
action VARCHAR(20),
message VARCHAR(380)
)
END_SQL
$dbh->do($sql);
And to insert a record using values I've determined elsewhere:
$dbh->do('INSERT INTO seenDB (nick, rawnick, channel, action, message, date, time) VALUES (?, ?, ?, ?, ?, ?, ?)', undef, $nickString, $rawnickString, $channelString, $actionString, $messageString, $dateString, $timeString);
So, when the script needs to update, I'd like to update all of these fiends at once, but right now the only thing that works is one at a time, using syntax I got from the tutorial:
$dbh->do('UPDATE seenDB SET time = ? WHERE nick = ?',
undef,
$timeString,
$nickString);
I've tried the following syntaxes for multiple fields, but they fail:
$dbh->do('UPDATE seenDB (rawnick, channel, action, message, date, time) VALUES (?, ?, ?, ?, ?, ?)', undef, $rawnickString, $channelString, $actionString, $messageString, $dateString, $timeString);
and
$dbh->do('UPDATE seenDB SET rawnick=$rawnickString channel=$channelString action=$actionString message=$messageString date=$dateString time=$timeString WHERE nick=$nickString');
Is there a better way to do this?
You can update several fields at once in pretty much the same way as you update a single field, just list them comma separated in the update, something like;
$dbh->do('UPDATE seenDB SET rawnick=?, channel=?, action=?, message=?, date=?, time=? WHERE nick=?',
undef,
$rawnickString,
$channelString,
$actionString,
$messageString,
$dateString,
$timeString,
$nickString
);
I am attempting to run a query that uses bind variables against a mysql database engine. I am wondering how I can tell the engine to "reset" the bind variable assignments. I'm sure an example will explain much better than my poor brain.
Here is the query:
INSERT INTO site_support_docs
(
ASSET_ID,
TIME_STAMP,
SITE_NAME,
DOCUMENT_NAME,
DOCUMENT_LOCATION,
DOCUMENT_CONTENT,
DOCUMENT_LAST_MODIFIED
)
VALUES (?, ?, ?, ?, ?, ?, STR_TO_DATE(?, '%M %e, %Y %r'))
ON DUPLICATE KEY UPDATE asset_id = ?,
time_stamp = ?,
site_name = ?,
document_name = ?,
document_location = ?,
document_content = ?,
document_last_modified =
STR_TO_DATE(?, '%M %e, %Y %r')
My problem is that the eighth "?" is interpreted as a new bind variable when there are only seven. Anyway, I guess I can revert to using the actual values... but, I'm sure there is a better way.
Matt
MySQL offers a "VALUES()" function that provides the value which would have been inserted had the duplicate key conflict not existed. You don't need to repeat the placeholder then.
INSERT INTO t VALUES (?) ON DUPLICATE KEY UPDATE x = VALUES(x);
http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html#function_values