Skip to main content
added 17 characters in body
Source Link
Michael Borgwardt
  • 51.4k
  • 13
  • 127
  • 178

Don't give DROP DATABASE or DROP TABLE privileges to the DB user you use for Grails.

It might also be a good idea to withhold most other privileges (other then INSERT, SELECT, DELETE) in production, as you don't want Grails to automagically do an ALTER TABLE operation that locks an important table for 30 minutes...

Don't give DROP TABLE privileges to the DB user you use for Grails.

It might also be a good idea to withhold most other privileges (other then INSERT, SELECT, DELETE) in production, as you don't want Grails to automagically do an ALTER TABLE operation that locks an important table for 30 minutes...

Don't give DROP DATABASE or DROP TABLE privileges to the DB user you use for Grails.

It might also be a good idea to withhold most other privileges (other then INSERT, SELECT, DELETE) in production, as you don't want Grails to automagically do an ALTER TABLE operation that locks an important table for 30 minutes...

Source Link
Michael Borgwardt
  • 51.4k
  • 13
  • 127
  • 178

Don't give DROP TABLE privileges to the DB user you use for Grails.

It might also be a good idea to withhold most other privileges (other then INSERT, SELECT, DELETE) in production, as you don't want Grails to automagically do an ALTER TABLE operation that locks an important table for 30 minutes...