You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to scope schema and table renaming for a whole Configuration through Settings is nice for multi-tenancy but not for sharding. Users who are sharding their tables should be able to rename the "base table" on the fly for ad-hoc usage. Example:
SELECT*FROM t1 -- t1 is renamed from tUNIONSELECT*FROM t2 -- t2 is renamed from t
In the above example, the table T is renamed twice in the same query, once to T1, and once to T2.
Note that in this context, renaming is not the same as aliasing! Renaming is only performed in Java memory prior to rendering SQL, whereas aliasing is performed in the SQL statement itself.
As table renaming is not really a SQL DSL feature, the rename() method should be generated onto generated tables only, instead of being declared in org.jooq.Table
The text was updated successfully, but these errors were encountered:
Being able to scope schema and table renaming for a whole
Configuration
throughSettings
is nice for multi-tenancy but not for sharding. Users who are sharding their tables should be able to rename the "base table" on the fly for ad-hoc usage. Example:In the above example, the table
T
is renamed twice in the same query, once toT1
, and once toT2
.Note that in this context, renaming is not the same as aliasing! Renaming is only performed in Java memory prior to rendering SQL, whereas aliasing is performed in the SQL statement itself.
As table renaming is not really a SQL DSL feature, the
rename()
method should be generated onto generated tables only, instead of being declared inorg.jooq.Table
The text was updated successfully, but these errors were encountered: