Cannot INSERT into table containing single AUTO_INCREMENT field about jooq

[lukaseder]

Thanks for reporting this. In the SQL standard, this is not allowed,
see 7.1 here:
http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt

But of course, jOOQ should support such deviations from the standard,
if any of the underlying databases support it too. This won't be a
trivial change, though... I'll see what can be done

2012/6/15 cowwoc
[email protected]:

FieldMapsForInsert.isExecutable() returns false if

INSERT INTO foo VALUES ();

is invoked, but this is completely legal for tables containing a single AUTO_INCREMENT field.

---

Reply to this email directly or view it on GitHub:
#20

[cowwoc]

Now that you mention it, I don't mind inserting NULL into auto-generated keys (if this is what the standard says I should do) so long as all databases support it.

The hard part was figuring out how to get the desired behavior at all (whether I was using JOOQ or straight JDBC). I just happened to stumble upon VALUES() before VALUES(NULL) but it could have easily been the other way. Feel free to not implement this feature (so long as all databases support the alternative).

[lukaseder]

I'll have to think about this again. This will be tracked as issue #1506:
https://sourceforge.net/apps/trac/jooq/ticket/1506

See also #21 for potential side-effects of this issue

[lukaseder]

This ticket will be duplicated by #1506 after ticket migration from Trac