Still missing files about sql-to-jdl HOT 4 CLOSED

You are using postgresql but I only support mysql.

I think it is possible to support it but you need to check.
Can you try to create postgresql repositories that gives same data contract as current repositories?
Then you can use @ConditionalOnProperty of Spring to either enable postgresql or mysql and add a property in application.yml
(but in fact it might still not compile due to missing jooq classes... -> instead I could include those generated classes in codebase and set jooq as false to auto-generate)

from sql-to-jdl.

Hi Yoann,
thanks for you reply, I completely miss that Postgres is not supported. So, if I'm not wrong, are you suggesting that if InformationSchemaRepository would be an Interface, it should be enough to rewrite the actual queries taylored on MySQL Information_schema to retrieve from some Postgres metadata system tables:

• TableRelationInformation and its properties:
  private final String tableName;
  private final String columnName;
  private final String referencedTableName;
  private final String referencedColumnName;

• ColumnInformation
  private final String name;
  private final String type;
  private final String collation;
  private final boolean isNullable;
  private final boolean isPrimary;
  private final boolean isUnique;
  private final String defaultValue;
  private final String extra;
  private final String comment;

• TableInformation
  private final String name;
  private final String comment;

and finally the list of all table name to feed the getAllTableName method?

TIA,

R

from sql-to-jdl.

Yes exactly, it would be necessary to have InformationSchemaRepository as an Interface, then use a configuration class that expose beans of that interface, both on Conditional but only one at once (depending on option mysql or postgres).

After there is the issue of compiling the code when jOOQ generated code is missing.
For now you can either simply delete the mysql code in your local pc, do a bridge with postgres and the rest should be alright.

from sql-to-jdl.

Closed as not supported but can be done manually

from sql-to-jdl.