Django has a shell that automatically loads all model objects. If you've got a decent shared-nothing architecture and point your config to the live DB (bad idea, but for the sake of argument...) that's effectively a REPL for the webserver.
For that matter, you can get the same effect with the MySQL prompt and a shared-nothing PHP architecture.
Comments
Django has a shell that automatically loads all model objects. If you've got a decent shared-nothing architecture and point your config to the live DB (bad idea, but for the sake of argument...) that's effectively a REPL for the webserver.
For that matter, you can get the same effect with the MySQL prompt and a shared-nothing PHP architecture.
>For that matter, you can get the same effect with the MySQL prompt and a shared-nothing PHP architecture.
I see how you could, say, drop a user from the users table using this; but how would you fix a login bug like the one under discussion?
If you meant "How do you find out it was in the registration check?", that's what the slow query log and query profilers are for...