The interface is simple and very nice when reading database contents. Much nicer-looking than Navicat, albeit with less features. I don’t very much like the interface or the way the tables are laid out or the fact that each table opens up a new window, making for a very cluttered workspace. It’s not that great-looking but will do pretty much anything you need and has the advantage of also tackling Mysql databases so if you use both Mysql and SQLite like we do, you only need one tool. Though there is a sale of the Premium Essentials right now in the App Store. This is a capable but very pricey option. I just had to include it here because it’s so great and I work with it everyday monitoring and tweaking Doghouse performance. It doesn’t yet have support for SQLite but it’s in the works. And do us all a favour and donate something to the developers to keep them upgrading this wonderful product.
If you work with Mysql databases, do yourself a favour and get it now. This is the best tool for Mysql databases on the planet, no exceptions.
#SQLPRO FOR SQLITE FOR WINDOWS PRO#
Sure, you can use the terminal and issue all sorts of weird commands to manipulate your databases, but c’mon, who doesn’t love a GUI? Sequel Pro So, on to the most important thing, the GUIs or Graphical Tools for manipulating SQLite databases. You can find lots of good articles on SQLite usability and Mysql vs SQLite comparisons so I won’t bother, instead I’ll write about the Graphical Tools you can use to manipulate these databases. It offers all the simplicity of a file-driven database (Excel, CSV file, Access, etc) with none of the shortcomings, namely it allows for relational databases as well as constraints and triggers.
#SQLPRO FOR SQLITE FOR WINDOWS PORTABLE#
It’s extremely easy to set up, lightweight and very portable since the whole database consists of a single file and there are no server connections to worry about. This is, obviously, a big simplification, but not a bad starting point.
I read somewhere that the rule of thumb is that if your database takes less than 100,000 (100K) hits a day, then you’re find going with SQLite. But it’s perfect for portable applications and web sites that rely mostly on reading and not writing data. It’s not for every project, especially ones that require a lot of inserts or updates to your database. But, lately, I’ve had a lof of dealings with Ruby on Rails, whose default database engine is also SQLite and have found I really like it for certain tasks.įor those of you who are only interested in a Graphical Editor to be able to manipulate your pedia data, skip to the GUI tools below. Being a Mysql user for a number of years now I wasn’t really interested in this seemingly less capable new-comer. Working with Rails and the pedias I have had a chance to look more closely at SQLite, so I thought I’d write a short post about it.Īs you know, SQLite is the database ‘engine’ on which the pedias are based. I’m currently building the future Doghouse moderator section with Ruby On Rails. If you have any interest whatsoever in programming languages I really recommend giving Ruby a try (more on that in a future post).
Recently I started learning a wonderful and beautiful programming language called Ruby. I built the Doghouse infrastructure with these technologies. For the past year I’ve been chained in a dungeon, fed on a steady diet of MySQL and PHP.
0 kommentar(er)
