Quoting Paul Merlin <[email protected]>:
indexing-sql
============
I do not use this extension myself so I can't say a lot appart from the fact
that in the default build there are no unit tests running for real against a
database.
Only one implementation of indexing-sql is available for PostgreSQL.
Once java-
sql-generator will support Apache Derby we could work on the Derby
impl and have
unit tests in the default build (ie. without having to set up an external
database).
Paul is correct, currently indexing-sql only properly (= tested for
real) supports PostgreSQL (due to the fact that PgSQL is used at my
work). It generates the structure of database itself based on the
structure of Qi4j application, and it uses one schema for all tables.
There is little documentation, but currently no strings are used in
SQL generation, which was my main aim when finishing the indexing-sql
up.
TODO:
- let the user of indexing-sql have more easily understandable
control on when the database structure should be
created/wiped/re-indexed
- documentation
- support for other vendors as java-sql-generator will evolve (quite
little effort should be required from indexing-sql itself)
- if possible, better database structure
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
