[DataMapper] Restriction in dm-rails create/drop rake tasks

2010-07-02 Thread John E. Vincent
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

Re: [DataMapper] Restriction in dm-rails create/drop rake tasks

2010-07-02 Thread Martin Gamsjaeger
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 lusis@gmail.com wrote: I was curious what the reason for the localhost restriction on

[DataMapper] Re: Restriction in dm-rails create/drop rake tasks

2010-07-02 Thread John E. Vincent
snusnu, 1) Is there any objection to changing it? I'll poke around and see why AR has the same restriction. 2) I probably wasn't clear. You could use a regular SQL call over tcp/ 3306 or unix socket to create the database as opposed to using the system() call. Use the ruby mysql api directly. My

[DataMapper] Re: Restriction in dm-rails create/drop rake tasks

2010-07-02 Thread John E. Vincent
I just did some digging and AR no longer has the remote host restriction. Additionally, they no longer call system() to create the database. I can fork and request pull for fixing the remote host issue but it will take some time to change the system() logic. Assuming no one has any objections?