a.) Suggestions for prepared statements: when will it support addBatch/executeBatch (same for simple statement)?
 
b.) I'm currently reading that :-)
 
c.) Do you mean Statement.addBatch() / executeBatch()?
 
d.) seems interresting (for a developer and for the users)
 
about i18n, what do you mean by  "parm substitution"?
 
 
 
 -----Message d'origine-----
De : Campbell Boucher-Burnet [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 4 juillet 2003 21:31
À : wondersonic
Objet : Re: [Hsqldb-developers] Volunteer

All donated time gratefully accepted, I believe.  Please contact Fred to coordinate work.
 
Here are some areas that we intend to work on in, as far as I am aware, in approximate order of preference / priority / time sequence:
 
    a.) finish up baseline for prepared statements using intenal compiled parameteric statement objects
 
            - pretty much covered, but code reviews, comments, suggestions, contributed time always welcome, regardless

    b.) value pool refinements
 
            - probably pretty much covered, but same general comment as in a.) above
 
    c.) client-side batch execution implementaiton using facility now provided in CompiledStatementExecutor
 
            - like b, but much less so.  if you're fast on the uptake, this is something you could work on to good effect, right away.
    d.) simple query optimization
 
            - fairly straight-forward work if you know your relational algebra (e.g. things like convert select ... where something in (...) to select ... where pk = a union select ... where pk = b..., basically picking approximately best access path from multiple options, limiting size of inner nested loop joins, etc) , but really, really can benefit from lots of eyes and hands...all contributed time appreciated
 
    e.) database replication (see the HSQLDB/R link on the files page)
 
            - contact Fred.  I have no idea of the status on this
 
    f.) finer database object locking granularity / row versioning for statement-level read consistency and relatively lock free index traversal
 
            - multithreading the core, rather than using the current thread-safe whole-database lock per submitted sql
            - system change number (transaction id)  based row tagging / visibility predication
            - lots and lots of work...not for 1.7.2 RC, but hopefully 1.7.3 (no promises)
 
    g.) InnoDB/Oracle style data file format, allowing smaller, faster, more efficient checkpoints / better space managment, reuse / eliminate need to make complete backup of .data file every shutdown / reduce data file growth.
 
            - dreams for the future

    h.) generalized (virtualized) index interface, a. la GiST.  BTree indexing impl for file-based tables
 
            - dreams for the future
 
Obviously, there's also lots of work available for those that perhaps don't feel like diving straight into the core.
 
For instance:
 
- Further work on the resources package, compound error messages (parm substitution, enabling internationalization)
- More/better Test cases/ flesh out the existing, currently unused, not-yet-in-CVS Test Framework package / implement automated build / testsuite runs on sf compile farm
- Documentation updates
- Tool upgrades (esp TransferTool)
- Handle outstanding bug reports / patch submissions
 
----- Original Message -----
From: "wondersonic" <[EMAIL PROTECTED]>
Sent: Friday, July 04, 2003 12:18 PM
Subject: [Hsqldb-developers] Volunteer

> Hello,
> Since the last month, I have begun to work on a new project for the 1st
> french bank (BNP PARIBAS) that need to manage large amount of data
> (tables with 50-70 columns with over 1,000,000 of rows that can produce
> more data x10 to x50, the servers will have 4Gb of memory but must support
> parallel processing: at least the pre-defined amount of data plus 500Mb for
> other little processing). The currently selected solution to handle the
> treatments
> is the HSQLDB database.
>
> I've got a background of 4 years in Java and I've got some time.
>
> So here are my needs:
> - Handle data with the minimum amount of memory
> - Have a rock solid datatabase
> - And fast if possible ;-)
>
> What are yours?
>
> Thanks for your answer(s),
> Loic Lefevre
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> hsqldb-developers mailing list
>
[EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>

Reply via email to