Hi Jonathan,
Thanks for this information and offer. You obviously know our pain,
inside-out :-)
I am glad to report that 2 Tiki developers have expressed interest so far.
I am hereby passing on the link to Tiki dev-list :-)
http://code.google.com/p/power-architect/
Best regards,
M ;-)
On Mon, Jun 8, 2009 at 5:40 PM, Jonathan Fuerth<fuerth@sqlpower.ca> wrote:
> On Mon, Jun 8, 2009 at 12:29 AM, Marc Laporte <marclaporte@tikiwiki.org> wrote:
>> Tiki uses a database abstraction layer so it can be used with many
>> databases (PostgreSQL, Oracle, Sybase, SQLite) in addition to MYSQL.
>> However, support for anything but MySQL has become more & more
>> problematic. It's not strictly a chicken & egg problem because Tiki
>> once worked with non-MYSQL. However, without maintainers, it was lost
>> over time.
>
> I'm guessing one of the painful things you deal with is maintaining
> the create and upgrade DDL scripts for all those platforms. I've done
> this in the past (years ago now, thankfully) for several
> database-independent products. It's not fun.
>
> I'm the lead developer on Power*Architect, an open source data
> modeling tool that lets you develop your data model in a
> platform-independent and visual way, then "forward engineer" to
> several platforms (from your list, we support PostgreSQL, Oracle, and
> MySQL--Sybase and SQLite support would need a bit of work). You could
> use this to generate both create and upgrade scripts for all the
> supported platforms.
>
> I hope this can help you argue to keep PostgreSQL support. With a
> platform-independent data model, supporting multiple platforms is much
> easier. I've done the switch from hand-coded SQL to platform
> independent visual modeling on real projects, so I could give a bit of
> advice about how to approach the problem if any of the tikiwiki
> developers are interested in trying it!
>
> -Jonathan
>
--
Marc Laporte
http://MarcLaporte.com
http://TikiWiki.org/MarcLaporte
