The lack of enforceable foreign key constrains has pushed almost everything to MySQL 5 using the InnoDB engine.With TablePlus, you can easily import a CSV file to any SQL databases within a couple of clicks. I'd much rather see more effort put into supporting Postgres than MySQL 4, I very rarely encounter applications anymore as a consultant that run on MySQL 4. Only other things I could possibly ask for based on what I've seen so far is contextual menu support for the catalogs and tables in the sources pane on the left, and PostgreSQL support would be a huge plus. I'll continue evaluating it throughout the month. Currently a table gets created with a default 'id' column, and subsequent elements are added through ALTER statements. A way to define the data-engine type (MyISAM is typically default, but InnoDB is what you typically have to use if you want proper normalization and constraints) on newly created tables, and I'd prefer delayed commits when new tables are created. 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. 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. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |