I worked at one place where we used DbVisualizer. It's a paid product but it works with every type of DB. We often had to connect to SQL*Server, Oracle or MySql and it was nice to only use one tool.
I was explaining to someone yesterday that I almost exclusively use 'rails console' to query my data now. It force me to be familiar with my models and how to access them via Ruby. Kevin On Fri, Aug 31, 2012 at 9:42 AM, Guyren Howe <[email protected]> wrote: > If you are forced to use MySQL, I just discovered MySQLWorkbench, which > looks to be really useful also. > > > > On Aug 31, 2012, at 6:08 AM, Etienne de Bruin <[email protected]> wrote: > > Rubyists! > > The Google god seems to suggest that this tool is the best SQLite browser > out there http://sqlitebrowser.sourceforge.net/index.html > > This made me wonder how you guys work with your local DB's when > developing. I know migrations are the best way to create and alter > structures if you're Rails'ing, but how do you guys browse, truncate, > query, etc.? > > Etienne > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
