The way around the test data load is to import the data via csv.
Even loading a 1000 line script hangs the program for at least a minute. My 10MB Test Data Load script has never failed to hang the program (beachball) necessitating a force-quit. My only complaint at all about Querious is that it seems to be frightened of large sql files. The look and feel of both the editors are great, but for reasons mentioned below, I am still doing most of my editing in a different program. You can also open or create SQL files in a separate window that has all of the same features except for the table reference panel. You can also switch to a different table if you’re thinking quicker than the AI. Double clicking on a column will insert the name at the cursor. There’s also a context sensitive table reference panel that senses which table you’re referring to and lists all of the columns. The Query view gives you a SQL editor with all the usual bells and whistles: context sensitive highlighting, an intelligent (much more so than Workbench) auto complete feature. Finally, you can see table info and options – along with an exportable CREATE statement. Other tabs show you what triggers exist for tables and allow you to create or change them. You can also add, change, or delete these from this view. You can switch tabs to see primary keys, indexes, and foreign keys. Clicking on a table will show you all of the columns, their types, any constraints. Clicking on the database will show you a diagram of all the tables, with lines showing foreign keys and relationships between tables. Structure shows you the structure of the database and the tables. You have to refresh for each table to see a value.
#Querious review update
My only quibble with this is that the row count does not update automatically. A real time saver when you need to do a quick sanity check.Ĭlicking on the database itself rather than a table gives you a view of every table and view along with data size, index size, auto_increment count, and row count. This pulls down a list of all the columns in the table and allows you to write a quick WHERE clause to filter the data. From within that view, you can filter the results shown by clicking on the “show all’ button. Querious has 4 main views: Content, Structure, Query, and Server.Ĭontent allows you to view the content of tables and views just by clicking on an object in the sidebar.
On top of that, the import speeds are blazing fast. Being able to do it at all is pretty fantastic, but being able to clean and manipulate the data easily before import is amazing. My favorite feature? That would have to be the ability to easily import from csv. I switched to Querious and I couldn’t be happier. Honestly, after a few hours of live chats with tech support trying to make it work, I gave up on it.
For example, when using it to connect to a remote database, it insists on treating it like a localhost. It does have some shortcomings in terms of ease of use and importing data.
#Querious review free
It’s not bad at all and, for a free tool, it’s great. It’s still a great machine.įor a while, I had been using MySQL Workbench as my interface.
#Querious review pro
Up until the middle of the batting stats table, I had been running MySQL locally on my late 2012 MacBook Pro 15inch Retina, maxed out with the 2.6 i7 and 16GB of RAM.
Just some thoughts about the tools and services I am using for my project.
0 kommentar(er)
