My ical/ics calendar file viewer and exporter ICS Viewer was updated

v4.4
Bug fixes:
- Some dates from 'DTSTART;VALUE=…' were not processed correctly.

v4.5
Bug fixes:
- The app would crash when exporting a CSV into a non-writeable folder. When this happens, you'll now get an error message.

My ical/ics calendar file viewer and exporter ICS Viewer was updated

v4.3
Bug fixes:
- Some .ics fies seem to lack the time behind the date. That woud crash the app. When no time is present, 12:00:00 is taken as default.


My ical/ics calendar file viewer and exporter ICS Viewer was updated

v4.2
Bug fixes:
- In rare occasions empty lines are created inside a calendar file. These are now skipped.


My ical/ics calendar file viewer and exporter ICS Viewer was updated

v4.1
Bug fixes:
- When the connection to MySQL fails, the error message dialog would leave the sheet window hang without any controls.


My ical/ics calendar file viewer ICS Viewer is updated to version 3.9

v3.9
Bug fixes:
- Fixed a possible hang when choosing a date-range.


My ical/ics calendar file viewer ICS Viewer is updated to version 3.8

v3.8
Bug fixes:
- 'Last month' preference showed 12 months earlier, when in January of a new year.


My ical/ics calendar file viewer ICS Viewer is updated to version 3.7

v3.7
Bug fixes:
- A hang with the new initial date-range preference setting 'Current month' has been fixed.
- The possibility to use the new initial date-range preference setting has been fixed.
- Various UI improvements in the preferences window.

Some time ago I did a MySQL upgrade without thinking ... that was not funny. So I retraced what I did to get the new version up and running and wrote it down as a sequence of steps to follow, when I need to upgrade to the next higher version.

I published these steps on the page [Repair] MySQL Upgrade (Mac OS X) , so they might be of help to you too.

CSVviewer (formerly known as TABviewer) is a tool which shows the contents of text files, where data of each line is equally separated by either a semicolon, a comma or a tab-character.

You can download it here.

Again I needed to transfer all data from one server to another. I knew I documented the transfer of MySQL databases somewhere (it's deep inside in the Replication-how-to) and decided to post them again here, so they're quicker to find.

One can transfer MySQL databases in various ways:

1. Using mysqldump and zip + ftp
2. Zip the database itself + ftp (you might need to repair the tables after unzipping)
3. Use Navicat's Data Transfer module (not always good for tables with millions of records or blob data)

Personally, I prefer to use option 2, like below, in Terminal or an SSH session:

$ cd /var/mysql/ (or /var/lib/mysql/)
$ sudo zip -r ~/[database].zip [database]

Do this for each database that you want to copy. Then send all zip's per FTP to the new server.
Start an SSH session with the remote server and enter the following commands:

$ cd /var/mysql (or /var/lib/mysql/)
$ sudo unzip ~/[database].zip
$ sudo chown -R _mysql:admin [database]

For the above chown, check first with ls -l if _mysql:admin are the right owners. Then do this for each unzipped database.

Next, start Navicat and now you should see your databases in the connection of the new server. If not, you probably forgot to either do a Refresh Connection or the chown-command.

If you can access the tables and view data, good! If not, right click the table and choose Maintain->Repair Table->Quick or ->Extended and then try again.