I have methods that take a Record as an argument. This is because the
method can be entered from multiple other methods, each having their own
query. So in this case I don't always know if a certain field is present in
the Record. For this I created a helper method:
public static T
Hi,
I just fixed a bug (luckily before production use), where I did an update
to a table that has a unique index over two fields. I forgot one of those
in the where clause. Thanks to jOOQ, I can just look at everywhere the
given field is used and fix any more missing.
That got me wondering:
How about
INSERT INTO user_permissions(...)
SELECT ...
FROM PERMISSION_TABLE
WHERE
?
--
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
Maybe it does, need to contemplate it a little. I do not want to leak my db
schema to the outside world (yet the outside world is contrained by it, so
there is a fine line there somewhere). I think I need to extend the
JavaGenerator.
Looking
at
Hi all,
I am writing a JAX-RS application that will take inputs that are validated
by Bean Validation (JSR 349). As these inputs eventually will wind up in
the database, I thought it would be nice to use the column definitions from
my jOOQ generated classes to validate them. Before I start
On Monday, December 4, 2017 at 10:40:47 AM UTC+1, Lukas Eder wrote:
>
> I hope this helps,
> Lukas
>
> Sure does, thanks for the prompt reply!
Groeten,
Friso
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group
Hi,
I was wondering if it is possible to send two statements and have one
database roundtrip. More specifically:
Given (MySQL):
CREATE TABLE t (
id INT AUTO_INCREMENT NOT NULL PRIMARY KEY,
name VARCHAR(10) NOT NULL
);
I want to send this to the database:
INSERT INTO t VALUES (NULL,
Hi all,
On Friday, September 29, 2017 at 2:56:36 PM UTC+2, Lukas Eder wrote:
>
> That explains why it would be unwise for jOOQ to consider that "length"
> information for any type deduction.
>
> The "global" type conversion mechanism that you could use would be to
> create your own
Hi,
Sorry for the late reply, I find myself doing something like this
regularly:
DSL.using(config).transaction(t -> {
int inserted = DSL.using(t).insertInto(t).execute();
Preconditions.checkState(inserted == 1);
});
So I guess I could do with a insertSingle (insertChecked?); a
