>> Incidentally, for those things (scalable write/search/read of large data >> sets) which existing database engines do well, which one would you >> recommend?
Hmmm . . . . am I dumb enough to incite a database holy war? . . . . . Yeah, I am. Let me phrase it this way . . . . I have extensive experience with MySQL, Microsoft SQL Server, Oracle, and PostgreSQL. MySQL is simplest and free. PostgreSQL is awesome and free though the tools aren't quite as friendly as Microsoft and it doesn't scale up quite as far as Microsoft yet -- though it probably scales further than anyone on this list really needs. Microsoft has the best tools and the easiest integration with many things. Oracle scales further but it's tools are not as good and it has some really odd capability holes. Or . . . . Never sneer at MySQL if someone wants it and it fulfills your requirements (though it won't cut it for AGI fairly quickly). If you're a LAMP/*nix aficionado and hate Microsoft, go PostgreSQL. If you're a Microsoftie, it's not a bad way to go and has many advantages. But don't use Oracle, the scaling advantage is *NOT* worth the costs (money, time, effort, and frustration). ----- Original Message ----- From: Russell Wallace To: [email protected] Sent: Wednesday, February 21, 2007 9:33 AM Subject: **SPAM** Re: [agi] Development Environments for AI (a few non-religious comments!) On 2/21/07, Mark Waser <[EMAIL PROTECTED]> wrote: and I think that there are a whole bunch more of similar cases that add up and add up and add up. Did you have to write code to load and save from memory to disk (both for swapping and semi-permanent purposes)? Are you confident that you know and have all the tricks necessary to scale up that enterprise Dabs already have (effectively for free to you)? And what about concurrency? Is your architecture designed *from the ground up* to allow controlled parallel, simultaneous operation? Incidentally, for those things (scalable write/search/read of large data sets) which existing database engines do well, which one would you recommend? For example, I remember hearing years ago that MySQL should be avoided other than for read-only operation due to lacking adequate transaction handling, but I've also heard it's improved a great deal in the meantime, is that the case? ------------------------------------------------------------------------------ This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?list_id=303 ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?list_id=303
