Sqleditor on Angus Thinks

SQLEditor 4.0

Mon, 13 Jun 2022 00:00:00 +0000

After a bit of a gap, SQLEditor 4 is now pretty much at the point of a public release.

Thanks to everyone who has been trying beta versions and the most helpful bug reports!

Rails Migrations and Schemas

Fri, 26 Feb 2010 00:00:00 +0000

A schema.rb file is typically a ruby script containing a call to the ActiveRecord::Schema.define method.
A rails migration is a ruby class which inherits from ActiveRecord::Migration and contains a method called up

The useful fact that I realized only after doing some ultimately unnecessary work today is that because the schema file contains a method call, it’s actually easier to extract the information from it than with a migration (which needs SQLEditor to figure out a class name and then call the up method)

SQLEditor 1.6 final

Wed, 06 Jan 2010 00:00:00 +0000

So, if you’ve seen SQLEditor recently, you’ll hopefully have seen that there is a new version out: version 1.6 . This got released just at the beginning of December 2009

1.6 is something that I’ve been working on now for a long time, it is essentially (the unreleased) version 1.5 with improvements and updates. In particular it contains a SQL parser that was written using ANTLR and a new JNI based system for using JDBC drivers with support for Java 6 JDBC drivers.

SQLEditor 1.4.4 Released

Thu, 30 Apr 2009 00:00:00 +0000

SQLEditor 1.4.4 was just released on Tuesday, the main feature improvement is the support for compound foreign keys. I posted a bit about this before and the final version is pretty much the same as I described.

Unfortunately there were a couple of bugs that slipped through relating to clicking objects. :-(

These are going to be fixed in a point release that should appear soon.

The new version is available from the automatic update system or download here:

SQLEditor: Compound Foreign Keys

Thu, 09 Apr 2009 00:00:00 +0000

The newest version of SQLEditor (1.4.4b1) now has support for compound foreign keys. This is something that people have been asking about for a while now, so I’m pleased that it got included.

There are some things that may need to be improved, but I’m fairly happy with the first revision of this.

[caption id=“attachment_400” align=“alignnone” width=“443” caption=“Diagram showing compound foreign key”][/caption]

The compound foreign key object is a new table level object that you can add from the Object menu just like a field or index. Then you drag from the foreign key to the target table. Finally you use the inspector to create pairs of columns to link together.

SQLEditor 1.4.3b3

Mon, 22 Dec 2008 00:00:00 +0000

So, it’s coming up to the holidays, but there is time for another SQLEditor release.

1.4.3b3 (snappy numbering, yes?) is pretty much a bug fix release. I think that the index creation problems that were happening have now been fixed, plus better handling of when to create indexes. It should now correctly figure out if fields are indexed and shouldn’t now add duplicates (or worse attempt to add duplicates)

There is also the addition of the simulate mode for database export. This isn’t exactly new, because it’s been available in some development builds, but it has now appeared in a release version. Simulate mode runs the entire export as normal, except that instructions that alter the database aren’t actually sent to the database to be executed. The instructions are recorded though, so you can see what would have happened in the status window log view.

MySQL before 4.1?

Mon, 01 Dec 2008 00:00:00 +0000

This graph appears to show that mostÂ people polled (97%) are using MySQL 4.1 or later

This second poll shows, again, that most people (89%) are using 4.1 or later.

The thread at the PunBB forum gives 95% of people polled using 4.1 or later.

The Mambo forum poll from 2006 gives 80% using versions after 4.1 (with 8.5% don’t know or other)

Admittedly not scientific surveys (self selection, etc) but somewhat convincing.

This has an obvious implication on how to handle MySQL support, in particular special casing to work around particular issues in early versions. This code adds complexity and in some unfortunate cases also bugs. The less there is, the better.

SQLEditor updates

Sat, 15 Nov 2008 00:00:00 +0000

I’ve just released a new version of SQLEditor yesterday, mainly as a bug fix release, but it’s definitely recommended to upgrade.

The new beta is 1.4.3b1 which was released 14th November. It fixes a number of bugs, including MySQL comments and some odd bugs relating to selecting tables using the drag selection method.

Download 1.4.3b1 (3.6MB DMG)

The current stable version is 1.4.2 which came out at the end of October. It fixed several significant bugs that people reported and made a few minor improvements.

Django Support

Thu, 06 Nov 2008 00:00:00 +0000

Several people have now asked for this, so it’s being really seriously looked at.

Plus I’m hopeful that it will be able to support the somewhat different but quite similar Google app engine model class format too

Having been working on this for the last few days, I can say that the Django plugin is moving towards a working state, the development version is now somewhat able to create and export a suitable python file.

SQLEditor releases

Thu, 16 Oct 2008 00:00:00 +0000

This is another quick update about SQLEditor releases in the near future.

1.4.2b1

Currently version 1.4.2b1 is in beta release, it offers a few specific improvements

Added support for editing MySQL character set and collation settings on fields and tables
Modified inspector on fields to use popup menu for selecting tabs
Fixed bug that prevented saving files after creating new foreign keys when referencing primary keys in tables with indexes under certain circumstances.

SQLEditor 1.4 Final Released

Fri, 01 Aug 2008 00:00:00 +0000

In case you missed it version 1.4 of SQLEditor was released back on July 8th.

If you’re using 1.3.9 you might like to consider upgrading.

The 1.3.9 upgrade system will be set soon to recommend this upgrade (though 1.3.9 doesn’t use sparkle, so it can’t actually do the upgrade for you)

SQLEditor 1.4 (3.6 MB DMG File)

Lots of great new features and various bug fixes and improvements to the existing ones.

SQLEditor 1.4b2

Fri, 17 Aug 2007 00:00:00 +0000

Another day, another beta. (Kind of)

SQLEditor 1.4b2 is now available, which is pretty much bug fixing against 1.4b1.

There were several issues with 1.4b1 including an annoying bug that would sometimes delete foreign key connectors when you deleted an unrelated table.

There are some fixes for other bugs which turned up and some improvements to undo/redo, to make it more stable when you undo or redo lots of things, one after the other.

What have I been doing recently?

Mon, 11 Jun 2007 00:00:00 +0000

Well no updates for a bit. Humm?

The main things I’ve been working on:

SQLEditor . Lots of things are being worked on. The user interface is being rewritten to improve speed and increase flexibility, the data layer is being rewritten to switch it to cocoa (instead of java), the JDBC code is being rewritten to make it use JNI instead of cocoa/java and a new crash reporting system based on Google BreakPad is being worked on. There are also some other things too like live source view and assorted bug fixes. 2) HTMLValidator . Also undergoing development. It recently moved across to use Sparkle (yey!) instead of the SQLEditor derived update system (which will also be replaced eventually). The final 1.0 release is due very soon now and several people have set in nice comments. 3) A new idea (still secret) :-)

SQLEditor 1.3.2

Wed, 17 Jan 2007 00:00:00 +0000

SQLEditor 1.3.2 received a very limited release to a few selected testers at the end of 2006. However there were some additional issues that needed a bit more work, so the current plan is for a 1.3.3 release before the end of January.

SQLEditor 1.3.1

Sun, 10 Dec 2006 00:00:00 +0000

SQLEditor 1.3.1 got released on Friday afternoon, this was really just a bug fix release which fixed a handful of problems that were identified. I think the only major fix was that the new UID system was slightly broken in that if you copied an object, or duplicated it in some cases, then SQLEditor would not always recreate the unique ID numbers that represent each object. This had the effect that if you copied an object, SQLEditor couldn’t distinguish between the objects when reloading and so all connectors would be attached to the original object and not the new one. An unfortunate bug. :-(

MalcolmHardie Solutions Weblog

Tue, 31 Oct 2006 00:00:00 +0000

About the new MalcolmHardie Solutions weblog.

The new weblog will contain posts about SQLEditor and other products.

If you already reading Angus Thinks you probably don’t need to read the MalcolmHardie weblog as well because all the posts on the MalcolmHardie Solutions weblog will appear on Angus Thinks.

This mirroring is done using the xmlrpc api and code from the blogger api plugin for wordpress

static link library to replace dylib in mac os x

Thu, 26 Oct 2006 00:00:00 +0000

This post on the xcode-users list explains a neat trick on how to get xcode to link a static library instead of a dynamic library.

Imagine the circumstance: you want to use a particular non-standard version of a native library which is already part of the system; perhaps you want to use an old version with better compatibility, or a newer version with more features. The obvious thing to do is to take a static build of the library and add it your xcode project.

Running Oracle - The Solution

Wed, 10 May 2006 00:00:00 +0000

This follows on from my previous posting. Searching for an Oracle

This is kind of old news now, because it’s been in use since SQLEditor 1.2 was released. However I though I would explain how I solved the problem that I was having with installing Oracle.

The problem was that I didn’t have a linux machine with enough memory and at the time, qemu wasn’t really fast enough to run Oracle in a virtual machine.