in reply to Re: More on selecting rows with DBI...
in thread More on selecting rows with DBI...

Actually, I'm sorta new to MySQL...

I've used Oracle for the past years and there are a number of ways that this can be implemented on the database side (alot harder than LIMIT, BTW) by using PL/SQL. Now that I've been forced to use other DBMSs (MySQL being one of them), I'm trying to cut down to the least common denominator of SQL in order to maintain a certain degree of portability between the systems.

DBI has been great as far as portability, but I have found that my Oracle vices have prooven to be rather disappointing at times, since DBD::Oracle allows you to do fancy Oracle proprietary stuff (like selects within selects for instance)...

Oh, if only the DBMS vendors could agree on ONE PLAIN FLAVOR OF SQL it would make my life sooo much easier...
  • Comment on RE: Re: More on selecting rows with DBI...

Replies are listed 'Best First'.
RE: RE: Re: More on selecting rows with DBI...
by perlmonkey (Hermit) on May 02, 2000 at 11:23 UTC
    Oh, if only the DBMS vendors could agree on ONE PLAIN FLAVOR OF SQL it would make my life sooo much easier...

    I think this will happen about the same time Microsoft voluntarily open sources and GPLs Windows along with porting Office to Linux.

    It is too bad though. Standard SQL would make life a lot easier for us all.

    In the mean time maybe you can keep all the database specific code in one module, and dynamically require that library depending on which DBD you are using. So that way you should really be able to utilize the power of each database, but still maintain a some-what portable app. Then you can create a database module for each database the app will be using.