Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let expression in <forcedType/> match PostgreSQL domains #3486

Closed
axelfontaine opened this issue Jul 30, 2014 · 3 comments
Closed

Let expression in <forcedType/> match PostgreSQL domains #3486

axelfontaine opened this issue Jul 30, 2014 · 3 comments

Comments

@axelfontaine
Copy link

Currently a column defined as

create table mytab (
  mycol mydomain
);

has to be matched to the underlying type of the domain, say text, instead of the name of the domain, in this case mydomain.

@lukaseder lukaseder added this to the Version 3.5.0 milestone Jul 30, 2014
@lukaseder lukaseder modified the milestones: Version 3.6.0, Version 3.5.0 Oct 7, 2014
@lukaseder lukaseder modified the milestones: Version 3.7.0, Version 3.6.0 Apr 8, 2015
@lukaseder lukaseder changed the title Let converters match PostgreSQL domains in forcedType Let expression in <forcedType/> match PostgreSQL domains Jun 24, 2019
@lukaseder
Copy link
Member

Related idea: Match the content of CHECK constraints: #8843

@lukaseder lukaseder added this to To do in 3.13 Other improvements via automation Oct 14, 2019
@lukaseder
Copy link
Member

lukaseder commented Dec 21, 2022

Finally looking into this now. It seems it already works? There had been a few improvements related to supporting UDTs in the code generator, so unsurprisingly, this now works for domains, too, at least in PostgreSQL. Will add integration tests for at least these dialects, too:

  • Firebird
  • H2
  • HSQLDB
  • PostgreSQL
  • SQL Server
  • YugabyteDB

Note:

@lukaseder
Copy link
Member

Yep, it works out of the box in all dialects, probably since jOOQ 3.14, when DOMAIN type support was added in jOOQ: #681.

Closing as duplicate of #681

3.14 Embeddable Types automation moved this from To do to Done Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants