Chris Devers wrote: > On Mon, 13 Jun 2005, Wiggins d'Anconia wrote: > > >>If you are completely new to SQL/DBs then you might start with MySQL, >>though I would recommend going with PostgreSQL. > > > I wouldn't. > > PostgreSQL is good, but it's pretty complicated, and this problem isn't > yet. No need to make it more complicated than necessary. MySQL is > simpler, but it's still a pretty complex piece of software, and setting > it properly (security considerations, etc) should be taken seriously. > > I suggest taking a look at SQLite, which is a way to do SQL operations > using flat-file storage. There's no datbase server to set up, just one > library file that Perl's DBD::SQLite will include: > > <http://www.sqlite.org/> > <http://search.cpan.org/dist/DBD-SQLite/lib/DBD/SQLite.pm> > > If you get started this way, you may find that it is more than enough to > meet your needs for quite a while. If you grow out of it, you can switch > to MySQL or PostgreSQL and, ideally, your Perl code should only need > minor revisions -- change the DBD::SQLite call to DBD::mysql or DBD::Pg, > maybe change some of your SQL statements, and that's about it. The logic > of the program should remain the same if you switch database backends. >
Fair points, I forget SQL::Lite since I wouldn't (need to) use it since I am already familar with the others. It sure would have been nice to have SQLite as a first step when I first learned :-). Though I still think if you have the time and desire to learn a database, starting with a server isn't a bad idea, but there is more learning curve in the matters Chris mentioned. http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
