-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy tables #1
Comments
By default Gstorm executes "CREATE TABLE IF NOT EXISTS" statement, so if table already exists, then it shouldn't be overwritten. Although, this would mean there has to be an |
Oh, nice. One more question. I've worked with some old databases that use abbreviations for table names. Is there a way to specify the name of the table?. E.g. class Person {String name, project}
def g = GStorm(sql)
g.stormify(Person, 'PRS_TBL') |
Nevermind. I just went through the code and noticed it doesn't support it. |
Thanks for taking a look at the source and raising the first issue as well :) . Currently the implementation is very minimalistic. I am keeping this issue open to add capability to specify table name. |
9c977db (v0.4) Adds support for specifying the custom table name, here is the example. @Table("people")
class Person { String name, project } |
Hi, is there any way to stormify an object but not create a new table? Would be helpful with legacy databases.
The text was updated successfully, but these errors were encountered: