Could we, please, step back and discuss requirements *before* we discuss these types of implementation technologies? Tom's requesting Java is one thing, as it's nearly ubiquitous for programmers, users, and platforms. It may not be your preference, but it does fit the bill. If we want general participation from the larger community (not just the LDSOSS list), then something more widely known is probably a good idea.
As for databases, what are the database requirements? If the program operation is to be done at the ward level, then we're probably (depending on the ward size) talking about 30-150 kids or so. If at the stake, then multiply that by 8 or so. Are those numbers sufficient to warrant a database? If so, what type (not brand)? Granted, I'm not a DBA, but isn't a flat file faster for those numbers? Although I work in security and R&D, these days, I was a once upon a time USAF Software Engineer and those 'managerial pre-architectural decisions' sometimes come back to haunt me... Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Welch >> >>> I've not used this framework so it may not be suitable. For the >>> database, we could use Derby or One$DB. Again, I'm totally open to >>> other ideas here. >> I would recommend that we ship with specific, small database, such as >> the two you refer to, but that as a design principle, we validate that >> we can easily install and run on one or more of the commercial caliber >> DB's such as MySQL. >We could use hibernate which is somewhat DB agnostic. It does not >"officially" support Derby or One$DB but reports are that it does work >with Derby. I just wonder of hibernate would be somewhat overkill. _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
