[R-sig-finance] MySQL and other RDBMSs

eric eric at ehlarson.com
Sat Nov 26 17:05:27 CET 2005


Andrew Piskorski wrote:
> On Sat, Nov 26, 2005 at 12:11:27AM -0500, Rob Steele wrote:
>
>   
>> MySQL is ideal for the write-once-read-thereafter scenario 
>> that research implies
>>     

>> True (that's what MySQL was originally designed for), except that it's
>> SQL dialect is pretty limited, and the database has various
>> misfeatures, e.g.:
>>
>>   http://sql-info.de/mysql/gotchas.html
>>
>> The limited SQL support might or might not matter to you, depending on
>> just what sort of data you're loading in and how complicated your data
>> model and queries are, but it's certainly something you should keep in
>> mind when picking a RDBMS.  Maybe that's been improved in MySQL 5.0
>> (which was just released a month or so ago), I don't know.
>>
>> If I didn't want to use PostgreSQL or Oracle, I'd be tempted to try a
>> lightweight embedded database like SQLite or Metakit:
>>
>>     

One  of the advantages of PostgreSQL is that it is relatively easy to 
port a PostgreSQL database to Oracle if needed.  Moving MySQL to Oracle 
is a much bigger challenge.



More information about the R-sig-finance mailing list