Hi Marcus, Sorry for the delay. And sorry for the confusion.
Indeed, as I mentioned in the previous email, for historic reasons, jOOQ treats the MySQL "catalog" (database) like a schema, because from a practical perspective, those databases look like schemata. So, without actual catalog support in MySQL, it probably makes no sense to specify any catalog at all (on MySQL). But as you've noticed, the catalog will be required on SQL Server. But the main conclusion is this one: 2017-03-11 13:58 GMT+01:00 Marcus Gattinger <[email protected]>: > So in the end I was not able to find exaclty one combination of elements > "inputCatalog", "inputSchema", "outputCatalogToDefault", > "outputSchemaToDefault" that work for both DBMS types. Hence I was forced > to use the solution of my previous post. > Yes, that's not easily possible right now. Some databases support: - Catalogs and schemas (e.g. SQL Server) - Catalogs only (e.g. MySQL) - Schemas only (e.g. Oracle) - None (e.g. SQLite) So, I suspect that this kind of confusion might be inevitable at this stage. Note that an alternative approach is to use the XMLGenerator or the JPAGenerator to generate jOOQ code from database independent resources (XML files or JPA annotations). Perhaps that's a better solution? The drawback here is that not all features are available yet (e.g. stored procedures). Lukas -- 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.
