in reply to Re: Re: (z) Separation of SQL code
in thread (z) Separation of SQL code

Well, as Abigail mentioned, if you use stored procs you can limit the amount of database-specific code to something very small.

At eCircles (unfortunately dead now) we had a web site with around 80k lines of perl code, of which 400 were database-specific (using Sybase::CTlib), and with table-driven definitions for each stored procedure (i.e. logical database request). And because we were using Sybase's RPC functionality to call the procs there was 0 risk of SQL injection as there was no SQL parsing involved anywhere in the execution path.

DBD::Sybase is capable of using the RPC functionality as well

Michael

Replies are listed 'Best First'.
Re: Re: Re: Re: (z) Separation of SQL code
by demerphq (Chancellor) on Sep 12, 2003 at 16:18 UTC

    DBD::Sybase is capable of using the RPC functionality as well

    If you ever get the time I would love to see an advanced Sybase DB tutorial on PM.

    please, please, please, pretty please with sugar on top?


    ---
    demerphq

    <Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
      Good idea - although I suspect that most of the DBD::Sybase users here really use MS-SQL... :-)

      Michael

      If you ever get the time I would love to see an advanced Sybase DB tutorial on PM.

      It might be interesting to know that all Sybase documentation is also available on the web at http://www.sybase.com/support/manuals/, at no charge and no sign up required.

      Obviously, this doesn't include DBD::Sybase.

      Abigail

        Yep, I have the reference manuals for the servers I use (ASE 12 and ASE12.4) bookmarked. The search feature is pretty nice as well.

        Obviously, this doesn't include DBD::Sybase.

        It should though....


        ---
        demerphq

        <Elian> And I do take a kind of perverse pleasure in having an OO assembly language...