Blog

I’d like to say thank you to everyone who helped make 2008 a great year.

Thank you to all of our customers for supporting development by buying SQLEditor, for sending in helpful comments (and bug reports) and for general encouragement.

Thank you also to everyone who has helped with development of SQLEditor, the program wouldn’t be what it is without you!

2009 should bring improvements and enhancements (and a shorter requested features list), plus I’m looking forward to being able to show you what I’ve been working on in the secret development versions.

Thank you all and best wishes for 2009,

Angus

PS: The beautiful christmas tree above is from Icon Drawer

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.

There is also a new feature which prevents fields and indexes being dropped (although it doesn’t prevent modification, use simulate if that’s what you want)

SQLEditor also now adds a line in the status window when an export fails complete with the instructions that were actually executed and the error that occurred. This information was always in the log, but it should be easier to see how SQLEditor has gone wrong (in the event that it does of course)

Finally some fixes for a few (hopefully unlikely) crashing bugs.

Download

3.6MB dmg File

Change Log
Product Notes
Expires
21st January 2009

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.