merlyn is totally right, but lemme elaborate. Looking at your types of data (large amounts of text and binary) the Berkeley system is going to be way too small for what you're working with. Think of the Berkeley DB as a hash table that's stored to disk; it's great for some things, but comparing it to a relational database is like comparing a car to an F-16.
With MySQL you'll be able to store massive amounts of text data in TEXT columns with virtually no limit - you can do the same for binary data using BLOB. Be warned though - coding for MySQL using the DBI driver is a lot trickier than using the Berkeley DB interfaces.
In reply to Re: SQL vs Berkeley
by LukeyBoy
in thread SQL vs Berkeley
by philou
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |