One important thing for us is to not take the data of MyOwnDB users as hostage. All data stored in MyOwnDB belongs to their respective users. As such, we found it as much a problem as some users that there was no export function. Well, this problem is no more. Although we plan to go much further, we currently provide the export of the data of a table to a csv file. You can export all data of a table or apply a filter to get only the data you want. We also added the possibility to export search results to csv files.

You can prepare everything as good as you want you'll always discover something when your application goes live and gets used by other people that beta tester. That's why I'm happy of the interest and the number of people signing up for a free account, and most of all, of the limited number of problems encountered. True, we've made 3 updates to the applications in the last 24 hours, but those fixed all issues encountered by users. The most annoying problem is that we can't accept details named "id", as it clashes with our internal structure.

I sent a link to MyOwnDB to Emily Chang, from Ehub, and she actually posted it on Ehub. Seems her site is quite popular as we got hundreds of visits from there!

I have published a screencast about linking entries in different tables in MyOwnDB. It first shows how the administrator should define it, and then demonstrates its use when managing data. You can define one-to-one and one-to-many relations, and the interfaces adapts itself according to circumstances (eg if there's no entry available for linking, the button to do it is hidden).

There's no internationalisation integrated in Ruby on Rails, but it is very easy to develop websites in multipple languages with it. I'll post here how I did translate the error messages generated by ActiveRecord validation rules At first, warning: I'm using an as yet unreleased translation plugin. The reason it is not yet available is that I haven't had time to package it right. I have a controller used to manage the translations, and I haven't had the time to really look for a solution to package it in the plugin.

Welcome to the MyOwnDB blog. News will soon be posted about what will be your prefered database component of your Web Office.