L
Lukas Eder
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
SEP 28
OCT 5
OCT 12
OCT 19
OCT 26
NOV 2
NOV 9
NOV 16
Oct 29, 2026
”Data Geekery” with JOOQ creator Lukas Eder
15:43

Josh LongHOST
You can say the client might send a select all from customers, but then the database will actually add and tenant equals whatever the
L
15:54Lukas EderGUEST
Instead of having a prefix on all your tables where you put the same table in multiple schemas, or you can even have different tables in the same schema with a prefix on the table name, where you completely separate the data using metadata, you can also separate the data per tenant with a column, which is a normal way to do things, right? So you have a tenant ID column, and depending on what tenant you are in your session, you can only see your own data, the data of the tenant.
L
16:21Lukas EderGUEST
And the idea of role level security, which is also implemented, by the way, by multiple databases like Oracle, Postgres have these features as well embedded in their databases.
L
16:30Lukas EderGUEST
So the idea is that when you're in some sort of session context where the tenant ID is 42 or whatever, you can only see the data for that tenant and you can only modify the data for the tenant.
L
16:44Lukas EderGUEST
If you're using Oracle, you're obviously going to use, if you want to pay that feature, you're going to use virtual private database, which is what the feature is called.
17 MINS LATER