John, 1) The restriction is there because that's how AR handles it too 2) I'm not exactly sure how you mean "this could be done by SQL"?
cheers snusnu On Fri, Jul 2, 2010 at 20:05, John E. Vincent <[email protected]> wrote: > I was curious what the reason for the localhost restriction on > dm:create and dm:drop in dm-rails. Padrino is actually using a port of > the dm-rails rake tasks and, in the process of troubleshooting a > different issue, I noticed this. I've made a pull request for the fix > in the padrino dm rake tasks and would be willing to port it over to > dm-rails. > > What was the validation/reasoning behind the restriction? > > As a side note, why is the mysql command-line used/required to do > this? If the user defined has permissions to create/drop databases, > this could be done via SQL and make the process even easier instead of > calling system(). > > You can see the changes I made to the padrino rake task here: > > http://github.com/lusis/padrino-framework/commit/b86930fcdd556fa57797c60ca2aa8c332fa1663c > > -- > You received this message because you are subscribed to the Google Groups > "DataMapper" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/datamapper?hl=en. > > -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
