There are a couple key things missing that I hope are added shortly. It's been stable, responsive, and mostly feature complete. I've only been using this for a couple of days for a project requiring me to do some renovation on a MySQL database backing a Symfony project. It's faster, it's got more features, and of course, it's free.
Querious map pro#
So while I'm going to be keeping an eye on Querious, I'll be using Sequel Pro going forward. And the CSV import works like a dream too. Not only that, I can type a SQL query, and edit the result set directly. Sequel Pro just wipes the floor with Querious in terms of performance. Or at least that's what I came to expect with Querious. Most of my database work is on hosted databases, so while my cable modem is pretty fast, I do always accept that it's not going to be super-responsive. Not only does it look great now, but it really flies. Well, I just couldn't believe what I was seeing. That's when I looked back up Sequel Pro which had spawned from CocoaMySQL.
Querious map update#
Without being able to add or edit rows to query results (still), and not wanting to type out INSERT or UPDATE statements, this was the only real way to manipulate the data, and with that out of the window I needed an alternative. The straw that broke the back for me was the last release with broke the ability to be able to add or edit rows in the content view (to be fair though this bug was fixed quickly). I have submitted bug reports numerous times, and to be fair occasionally I have had a reply - but not always. I can live with limitations if I know that stuff is coming, but it doesn't seem to be quick in coming.
Querious map software#
The thing is, it's beta software - I accept that - so it's going to be a bit lacking, but let's not forget it is not free beta software. It looks Mac-like, it does most of what I need to be able to do, and it was moving forward. So when Querious came along I was truly excited. CocoaMySQL was around then and wasn't too bad, but didn't have the feature set of Navicat, and then of course the development of it stopped. But it seems that for every beta release that comes along more problems turn up with it (this one seems to have broken the CSV import again).įor years I used Navicat, and for all it's flaws (the main one being it doesn't store passwords in the keychain), it worked and it was the best option around.
It looks great, it has a good feature set, and the early adopter price is right, which is why I bought a licence some months back.
Querious map full#
All of the columns shown in the list are the columns in the table the foreign key is being added to.In the columns editor window, select the Foreign Table that the key will reference.Double-click on any of the Columns, Foreign Table, or Foreign Columns columns of the row and a contextual window will popup.You can optionally enter a name for the foreign key, or leave it blank and have MySQL give the key a name for you.Click on the add button under the Foreign Keys list.Therefore, to create foreign keys on a table, first make sure the table type is set to InnoDB using the “Table Info” view. To limit a column’s role in the primary key to just a specific length of the column, enter the length in the Length column next to the column.įoreign keys are only supported on InnoDB tables in MySQL 5.For each of the colums you want to be in the primary key, simply click on the checkbox next to the column in the list.Separate the columns included in the index by commas.Click on the add button under the Indexes list.Select the table you want to add the index to in the Databases list on the left side of the window.The “Indexes & Keys” view is where you can change indexes, foreign keys, and the primary key on your tables.
0 kommentar(er)
