Lets paint the picture:
Scenario part 1 : Migrating a couple thousand stored procedures from database technology X to mysql
Scenario part 2 : Legacy system where the people who wrote it left a long time ago
Scenario part 3 : Developers sure can get real creative and invent all kinds of ways to get data (eg: having a stored proc which formulates a big query using concat after going through a bunch of conditions (fair enough), BUT the parts making up the different queries are stored in a table on a database rather than within the stored proc itself) … talk about KIS – Keep it simple!!
Scenario part 4 : This stored proc references 18 tables, 4 views, and another two stored procedures on 5 databases
Now close your eyes and try to imagine that for a few seconds, nah kidding don’t want you to hurt yourself.
I wonder, who’s gonna cover my health insurance if i go crazy? :)
mysql 02:55:47 DEV > call storedprocblahbla(‘I’,’am’,’going’,’crazy’);
ERROR 1052 (23000): Column ‘state_of_mind’ in field list is ambiguous
Sure thats REALLY REALLY helpful thanks :), you know what, lets just mysqldump -d -R -B db1 db2 db3 db4 db5 > /wherever/you/like and grep for column ‘state_of_mind’.
I love a challenge but facing migration of so many stored procs I’d really love to have something “GOOD” to debug them with.
The solutions I found were:
1. Illatis eclipse plugin for $40
works on linux, mac and windows but does show me a lot of:
“An error has occurred when activating this view
2. mydebugger for $50
works on linux and mac via wine
3. dbForge for MySQL for $50
works only on windows due to .net framework (kinda crap because I `hate` using the former)
any other ideas are very welcome, especially opensource ones but I can’t find anything.
I can always try setting up debugging using GDB but would rather try to avoid that.
MySQL stored procedure debugging, can I sue for going insane?,