Hmm, that's interesting. I personally prefer leaving stuff the way it is.
There are some weird syntaxes around there with PostgreSQL or DB2, where
you can use INSERT statements as table references, e.g. PostgreSQL:
SELECT * FROM (
INSERT INTO ...
RETURNING *
)
DB2:
SELECT * FROM NEW TABLE (
INSERT INTO ...
)
I'm not quite sure if such "inner INSERTs" are allowed to reference items
from the outer scope... SQL at its best ;-)
2013/9/13 Eric Schwarzenbach <[email protected]>
> If I perform a DSLContext.insertInto(table, fields) where the Field
> objects in fields collection are aliased, executing the insert fails
> because the names going into the insert statement are the alias names and
> not the actual column names. Would you consider this a bug? (My reason for
> aliasing the Field objects is because I use them also for another purpose;
> I'm not actually aware of a use for aliases in an INSERT statement.)
> ********
>
> --
> You received this message because you are subscribed to the Google Groups
> "jOOQ User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
