Hello everyone, I'm glad to announce that the `exp...

# exposed

[tapac]

Hello everyone, I'm glad to announce that the exposed-gralde-plugin is here with a very small but usefult gradle task which allows to generate tables definitions by existing scheme.
https://plugins.gradle.org/plugin/com.jetbrains.exposed.gradle.plugin

The main idea is allow easily migrate your large (or not so large) existing projects to Exposed.

Please check a documentation on github and share your ideas on things that can be improved/added to a gradle plugin. For now I think that it can be useful to generate/validate schemas or prepare migration scripts (like ShemaUtils do). What do you think?

The on of the next steps is to have intellij-idea plugin to have same things in the IDE, so share your thoughts about that too:)

P.S. There can be bugs for sure:)

[Bogdan]

Are there restrictions for non-free (paid) databases like in JOOQ? Can I generate a schema for ORACLE?

[tapac]

The only restriction as availability to connect to a database with jdbc:)

[Bogdan]

super

[spand]

The one man army continues!

[Bogdan]

exposedCodeGeneratorConfig { // documetation github
    // error
    configFilepath = "exposedCodeGeneratorConfig.yml"
    // there is only configFilepath, rename ?
}

[Bogdan]

Custom connection properties. until I found it until I found where to ask

[Bogdan]

so far caught this error: Could not connect to jdbc: oracle: thin: @ 192.168.0.150: 1521: ORCL, for user 'user', with properties {}: ORA-00604: error occurred at recursive SQL level 1 ORA-01882: timezone region not found

[tapac]

I'll look into it.

[rnett]

Any chance of pushing the generated code in example? It would be nice to have an example of what exactly is generated.

[dave08]

A nice thing to add might be using testcontainers + sql DDL files to pull up a db and generate the classes from it... @tapac. Sometimes we don't want the whole structure of the db in production (or don't want to open a connection to it...), just exporting the DDL might be better, also in integration tests we already have those DDL files commited (at least the main ones...)