[dhis2] MySQL and more

[Ola H. T. <ol...@st...>]

> Hi all
>
> Just wanted to give you guys some of my thoughts about JDhis 2

> I have used MySql, Php and EZ for webdevelopment for two sites recently,
> and I was very disapointed by the lack of functionality in MySql, it
> currently lacks:
> Foreign keys (difficult to enforce data integrity)
> Nested SQL quires (advanced SQL quires might be difficult to make)
> Data locking (multiple access to same data concurrently can cause
> problems)
> ++ lots more. However, I have heard that this will be available in
> upcoming releases.

> Last tip. I have used Eclipse for my own development and I love that
> tool.. www.eclipse.org, nicely integrates with lots of servlet runners and
> other stuff (such as subversion and cvs).
>
> Tore

Hi,

Thanks Tore for contributing to the list, we still struggle to make this a
more active list.

Current version of MySQL now supports what you are mentioning. Have a look
here:
http://dev.mysqlcom/doc/mysql/en/InnoDB_overview.html :

"InnoDB is a transaction-safe, ACID-compliant storage engine with commit,
rollback, crash recovery and row-level locking capabilities. This version
is for users who want the high-performance MySQL database with full
transaction support. MySQL Standard is licensed under the GPL."

"'InnoDB provides MySQL with a transaction-safe (ACID compliant) storage
engine with commit, rollback, and crash recovery capabilities. InnoDB does
locking on the row level and also provides an Oracle-style consistent
non-locking read in SELECT statements. These features increase multi-user
concurrency and performance. There is no need for lock escalation in
InnoDB because row-level locks in InnoDB fit in very little space. InnoDB
also supports FOREIGN KEY constraints. In SQL queries you can freely mix
InnoDB type tables with other table types of MySQL, even within the same
query."

Anyway, we will develop a database independent application so we are not
bound to MySQL. An important goal for both the DHIS 1.4 and the
web-enabled 2.0 is to support all or at least most DBMSs.

However, MySQL seems like a good Open Source choice and we will use it for
the first development phase. The upcoming (around Christmas I think)
windows version of PostgreSQL will also be very interesting for us.

When it comes to IDE we have gone for Eclipse 3.0 and I am happy to hear
that you have great experiences using it.

Again, thanks for valuable input. I hope more of you out there are willing
to share your thoughts wit the rest of the list.

Ola