[jOOQ/jOOQ#15677] Make sure CHECK constraint ordering is stable

This commit is contained in:
Lukas Eder 2023-10-04 11:01:19 +02:00
parent 4bce9f79b7
commit 5e066d0a53

View File

@ -849,6 +849,7 @@ public class PostgresDatabase extends AbstractDatabase implements ResultQueryDat
"domain_id",
"base_id",
"typbasetype",
"conname",
"src"
)
.as(
@ -856,6 +857,7 @@ public class PostgresDatabase extends AbstractDatabase implements ResultQueryDat
d.OID,
d.OID,
d.TYPBASETYPE,
c.CONNAME,
when(c.OID.isNotNull(), array(constraintDef))
)
.from(d)
@ -868,6 +870,7 @@ public class PostgresDatabase extends AbstractDatabase implements ResultQueryDat
field(name("domains", "domain_id"), Long.class),
d.OID,
d.TYPBASETYPE,
c.CONNAME,
decode()
.when(c.CONBIN.isNull(), src)
.otherwise(arrayAppend(src, constraintDef))
@ -903,7 +906,7 @@ public class PostgresDatabase extends AbstractDatabase implements ResultQueryDat
.on(field(name("domains", "base_id")).eq(b.OID))
.where(d.TYPTYPE.eq("d"))
.and(d.pgNamespace().NSPNAME.in(getInputSchemata()))
.orderBy(d.pgNamespace().NSPNAME, d.TYPNAME)
.orderBy(d.pgNamespace().NSPNAME, d.TYPNAME, field(name("domains", "conname")))
) {
String schemaName = record.get(d.pgNamespace().NSPNAME);