Angus Thinks

Tag: SQLEditor

  • SQLEditor releases

    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.

    1.4.2b2

    1.4.2b2 is due fairly soon. The following improvements should definitely appear

    • Modified MySQL exporter to use ENGINE instead of TYPE for better compatibility
    • Comments now attached to fields when exporting MySQL
      (i.e COMMENT ‘xyz’ style)
    • Connector inspector is now displayed automatically when a new connector is created
    • More padding added to line click detection to make it easier to click on connectors
    • Better parsing of comments attached to mysql field

    There is also a bug relating to identifying objects in Postgresql when there is no schema when using some versions of that database system.This is currently planned to be included but hasn’t actually been finished yet. If the work on this bug gets completed this week it will appear in 1.4.2b2, otherwise it will get pushed to the next release.

    I think that’s everything that’s coming in the near future, there are some other things that I’ve been working on, but they’re more long term (mainly for 1.5), so not much to say yet.

  • SQLEditor 1.4 Final Released

    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

    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.

    I’ve also moved SQLEditor to Sparkle. Sparkle replaces an update system that I wrote myself and it should offer better update support as well as a nice html based ‘what’s changed’ window.

    SQLEditor also now tells people that it is a beta and exactly when it will expire. It probably should always have done this, but it does it now, which is probably good.

    There are also some minor fixes to the live source view, so that it changes with the document sql dialect and appears correctly when reopening existing documents.

    [Download] (3.4MB DMG File, changelog)

  • What have I been doing recently?

    Well no updates for a bit. Humm?

    The main things I’ve been working on:

    1) 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) 🙂

    4) Web site improvements for malcolmhardie.com. Some have been deployed, others are still waiting to be deployed. Although the biggest one which is almost entirely invisible is the rewritten order processing system, which now supports multiple different products and better management features. But only I (and my somewhat-trusted minions) will ever see it. 😉

    Then when I’ve not been working I’ve been playing Pikmen on my new gamecube. (Many thanks to Leynos!). I’ve wanted to play this game properly for years and years and it definitely meets and exceeds my expectations.

    Although I also played some theme hospital this morning using Parallels 3.0 (new release). It runs really nicely, although since it is an ancient game (1997) this shouldn’t be too surprising. I hope to try out some of my other really old games to see how they perfom under parallels.

  • SQLEditor 1.3.2

    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

    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. 🙁

    It has now been fixed, along with slight improvements to image saving and a fix for a menu shortcut not being correct. The latter was an odd problem in that a shortcut was set, but it actually conflicted with an existing shortcut and the cocoa menu system is smart enough not to display the same shortcut for more than one menu.

    [Download] 2.8MB DMG

    For some reason also I don’t think I posted about the 1.3 release. But the 1.3 release was posted on November 23rd and is the first non-beta release to be released since May 2006. It rolled all of the improvements that had been made during the beta testing phase into a new release and is definitely worth upgrading (especially since the upgrade is free). However the 1.3 release has been superceded by the 1.3.1 release, so download that instead.

  • MalcolmHardie Solutions Weblog

    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

    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.

    However this typically won’t work. The linker will choose the system version instead because by default it looks in all possible locations for a dynamic library first before looking through the same list of locations for a static library. If there is a dynamic library in any of the search locations it will always get chosen. There are some good reasons for this, but what if you really want to include your own statically linked version?

    The answer is to add the -Wl,-search_paths_first flag to the other link flags option (under linking in target settings).

    When this is set each possible location for a library is inspected first for a dynamic library and then for a static library. This means that the static library will get linked correctly.

    It’s not exactly something that will be needed frequently though.

    Edit: Apple have a technical Q&A article (1393) on this very subject which appeared a couple of days back and which I somehow missed.
    It offers this exact method. [Link]

  • Running Oracle – The Solution

    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.

    The first strategy I used was to upgrade the memory in my linux box (Cetaganda) to 512 MB. This solved the memory problem and meant that the testing could continue.

    Then Parallels Workstation was released, which was able to run Oracle XE in a virtual machine fast enough for regular use. It also uses a different IP address than the host machine, which is useful in itself for testing.

    Parallels is definitely the answer to this problem, I don’t need to switch on another machine, there is no additional noise and the performance is excellent for my purposes. I’m even considering adding the loading of the VM to the unit test setup so it will load automatically before the test cycle starts.

    I’ve also got MySQL and Postgres running inside virtual machines.