-
Notifications
You must be signed in to change notification settings - Fork 93
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
No tables created #23
Comments
Hey folks... I really wanted to try grails, but you seem not interested in that. From the grails site: Simply unpack the zip file and run either ./grailsw run-app (Unix-like systems)It isn't working at all. No configuration info was provided. Isn't it supposed to work out-of-the-box? Do I need to create the tables? Hope to hear something from you, |
Those error messages appear to be an issue with Hibernate 4 and the H2 in-memory database, but it doesn't stop the application from running. Does the application start if you make the following change in the // Change this line:
run: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
// To this:
run: false, Then run: $ ./grailsw clean
$ ./grailsw run-app |
I don't know why your server is exiting right away but I am not sure that it is related to the error messages related to dropping constraints. When I run the app on OS X I do see the error messages about dropping constraints but the app works. I can verify that not only be interacting with the app but also by looking at the database and/or turning SQL logging on. Tables are in fact created and the app is functioning as designed. The errors about dropping constraints should be addressed, but they don't appear to be problematic in a way that prevents that app from functioning. |
The errors are about inexistent tables. I've tried what @caseyscarborough said without luck. The only difference is that after executing the command is not returning to prompt and the server seems to be running:
But:
I'm puzzled with the sample... |
I've cloned the repo and I get an error:
No server running. Did I miss something from README.md? DB scripts or something?
The text was updated successfully, but these errors were encountered: