Am Do., 12. Juli 2018 um 09:56 Uhr schrieb :
> The actual isse was that the derived table records would not implement
> UpdateableRecord and thus could not be used as the type in a class derived
> from DaoImpl.
>
Oh, I see now. Well, the problem is, the primary key is a lie :-) Check
this
Am Do., 12. Juli 2018 um 09:56 Uhr schrieb :
> The actual isse was that the derived table records would not implement
> UpdateableRecord and thus could not be used as the type in a class derived
> from DaoImpl.
>
Oh, I see now. Well, the problem is, the primary key is a lie :-) Check
this out:
Hi Lukas,
thank you for taking the time to check the issue.
To continue the development, I switched to individual tables with mostly
the same columns. My hope was to not have to implement so much boilerplate
code multiple times, but I probably overrated how much that would be.
The actual isse
Hi David,
I see, thanks for the explanation. Well, to my understanding, behind the
scenes, PostgreSQL stores copies of the base table for each inherited table
and replaces the original base table by a view of some sort. Querying your
base table yields:
QUERY PLAN
Hello Lucas,
the use case is I want to store typed metadata, e.g. numbers, strings,
boolean and geolocation, like this:
CREATE TYPE meta.metadata_type AS ENUM ('int32', 'float64', 'string',
'lnglat', 'boolean');
CREATE TABLE meta.metadata (
uuid uuid NOT NULL,
Hello David,
I'm assuming you plan to be using the code generator, which unfortunately
does not support PostgreSQL table inheritance yet. There are a few pending
feature requests:
- https://github.com/jOOQ/jOOQ/issues/2777
- https://github.com/jOOQ/jOOQ/issues/2782
Also related: Oracle OBJECT
Hello,
I have a postgres table with inheritance, I want to write a DAO for, which
I want to derive from DAOImpl. Now DAOImpl expects the table to be of type
UpdatetableRecord: DAOImpl, P, T>. What would
be the best way to implement a class working on an inherited table with
jOOQ?
Best
