Hi,

out software product targets different DBMS (e. g. SQL Server and MySQL), 
hence I'm facing the problem that some DBMS support schemas (like SQL 
Server) and others (MySQL) don't.
So my goal is to let jOOQ generate identical classes for the catalog and 
the schema implementation despite of the concrete database name (and schema 
if available) or DBMS. I do not want to create different source code 
branches for each DBMS.

I have partly achieved this by creating my own naming strategy (i. e. a 
class that derives from the DefaultGeneratorClass) and use it during the 
generation process:

<generator>
    <strategy>
        <name>MyGeneratorStrategy</name>
    </strategy>
    ...
<generator>


The names of the generated catalog and schema classes are now identical for SQL 
Server and MySQL (e. g. DefaultCatalog and DefaultSchema respectively).
But the generated catalog class contains the output catalog name (defined by 
the <outputCatalog> element) in its private constructor and the generated 
schema class contains the output schema name (defined by the <outputSchema> 
element) in its private constructor, respectively.

So how can I create a private constructor that do not use a string literal but 
rather a map of properties (a static map that is filled at application start 
time)?

Kind regards,
Marcus

-- 
You received this message because you are subscribed to the Google Groups "jOOQ 
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to