PHP5 and MySQL

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Spidah

    PHP5 and MySQL

    Looking at the list of changes made in PHP5 one of them is

    "Removed the bundled MySQL client library"

    Does anyone know exactly what this means? I assume we will still be able to
    code for MySQL as we do now?

    Thanks

    Hamilton


  • Louis-Philippe Huberdeau

    #2
    Re: PHP5 and MySQL

    Yes, but you need to specify the client library at compilation using
    --with-mysql=/usr/local (that's the default path I think)

    Spidah wrote:[color=blue]
    > Looking at the list of changes made in PHP5 one of them is
    >
    > "Removed the bundled MySQL client library"
    >
    > Does anyone know exactly what this means? I assume we will still be able to
    > code for MySQL as we do now?
    >
    > Thanks
    >
    > Hamilton
    >
    >[/color]

    Comment

    • Andy Hassall

      #3
      Re: PHP5 and MySQL

      On Thu, 31 Jul 2003 10:07:59 +1200, "Spidah" <nospam@eggstra .co.nz>
      wrote:
      [color=blue]
      >Looking at the list of changes made in PHP5 one of them is
      >
      >"Removed the bundled MySQL client library"[/color]

      Previously PHP came with the client portions of MySQL included in the
      distribution. This is no longer the case (apparently because of
      licensing issues).
      [color=blue]
      >Does anyone know exactly what this means? I assume we will still be able to
      >code for MySQL as we do now?[/color]

      Yes.

      Just because a MySQL client isn't included, this does not mean that
      MySQL support has been dropped - not at all, the MySQL PHP extension
      is there as before, and an improved version based on MySQL 4.1 is in
      development (the mysqli extension).

      All it means is you have to have an existing MySQL client installed
      (if your MySQL database is on the same machine then you've already got
      it, if not then it's no great hardship to install it), and you specify
      --with-mysql when compiling PHP, or possibly pass it the path to the
      client libraries if it's in a non-standard location.

      The situation in the Windows precompiled .zip version for PHP5beta1
      appears confused at the moment, as they've included the MySQL client
      libraries, but not included the MySQL PHP extension. I can't see any
      reason why this can't be worked out before PHP5 comes out of beta.

      Looking in the latest php5 .zip package from snaps.php.net, that does
      now appear to include the php_mysql.dll PHP extension. (And also,
      still, the MySQL client library).

      [ What's the betting that this'll be the new FAQ to replace
      register_global s ;-p ]

      --
      Andy Hassall (andy@andyh.co. uk) icq(5747695) (http://www.andyh.co.uk)
      Space: disk usage analysis tool (http://www.andyhsoftware.co.uk/space)

      Comment

      • Spidah

        #4
        Re: PHP5 and MySQL

        Thanks to both respondents for the clarification.

        Sounds like the new regime will be much as I thought.

        Of course, I can't actually see how licensing issues would be behind the
        change when both PHP & MySQL(most versions) are both open source and
        provided free of charge. Presumably the dll included in the latest builds of
        PHP5 is to ensure support for at least the free versions of MySQL is
        continued as before.

        Hamilton


        "the web site for web sites"

        "Andy Hassall" <andy@andyh.co. uk> wrote in message
        news:pjhgivsn6f 22k65a8ipegeaj0 0grmcib2m@4ax.c om...[color=blue]
        > On Thu, 31 Jul 2003 10:07:59 +1200, "Spidah" <nospam@eggstra .co.nz>
        > wrote:
        >[color=green]
        > >Looking at the list of changes made in PHP5 one of them is
        > >
        > >"Removed the bundled MySQL client library"[/color]
        >
        > Previously PHP came with the client portions of MySQL included in the
        > distribution. This is no longer the case (apparently because of
        > licensing issues).
        >[color=green]
        > >Does anyone know exactly what this means? I assume we will still be able[/color][/color]
        to[color=blue][color=green]
        > >code for MySQL as we do now?[/color]
        >
        > Yes.
        >
        > Just because a MySQL client isn't included, this does not mean that
        > MySQL support has been dropped - not at all, the MySQL PHP extension
        > is there as before, and an improved version based on MySQL 4.1 is in
        > development (the mysqli extension).
        >
        > All it means is you have to have an existing MySQL client installed
        > (if your MySQL database is on the same machine then you've already got
        > it, if not then it's no great hardship to install it), and you specify
        > --with-mysql when compiling PHP, or possibly pass it the path to the
        > client libraries if it's in a non-standard location.
        >
        > The situation in the Windows precompiled .zip version for PHP5beta1
        > appears confused at the moment, as they've included the MySQL client
        > libraries, but not included the MySQL PHP extension. I can't see any
        > reason why this can't be worked out before PHP5 comes out of beta.
        >
        > Looking in the latest php5 .zip package from snaps.php.net, that does
        > now appear to include the php_mysql.dll PHP extension. (And also,
        > still, the MySQL client library).
        >
        > [ What's the betting that this'll be the new FAQ to replace
        > register_global s ;-p ]
        >
        > --
        > Andy Hassall (andy@andyh.co. uk) icq(5747695) (http://www.andyh.co.uk)
        > Space: disk usage analysis tool (http://www.andyhsoftware.co.uk/space)[/color]


        Comment

        • Peter James

          #5
          Re: PHP5 and MySQL

          > Of course, I can't actually see how licensing issues would be behind the[color=blue]
          > change when both PHP & MySQL(most versions) are both open source and
          > provided free of charge. Presumably the dll included in the latest builds[/color]
          of[color=blue]
          > PHP5 is to ensure support for at least the free versions of MySQL is
          > continued as before.[/color]

          Reminiscient of George Orwell's Animal Farm, some licenses are more "free"
          than others. MySQL ships with a GPL license, which does not play nicely
          with PHP's BSD-style license. (GPL would seem to imply that the simple act
          of linking PHP to the MySQL client libraries would make PHP a derivative
          work of MySQL... ya, okay.)

          Not all open-source projects are created equal. :-)

          For more information on the MySQL / PHP debundling and license issues, have
          a look at http://www.phparch.com/mysql/

          HTH.
          Pete.

          --
          Peter James
          petej@phparch.c om

          php|architect
          The Magazine for PHP Professionals
          The site for PHP professionals, Magazine, Training, Books, Conferences



          Comment

          • Spidah

            #6
            Re: PHP5 and MySQL

            Exactly what does this mean for PHP scripters?

            If I write a PHP script that uses MySQL as its database engine is my script
            considered a derivative work of MySQL (meaning I need a commercial MySQL
            licence if I want to sell the script)?

            Regards
            Hamilton


            "Peter James" <petej@shaman.c a> wrote in message
            news:vih7j0cg47 rs21@corp.super news.com...[color=blue][color=green]
            > > Of course, I can't actually see how licensing issues would be behind the
            > > change when both PHP & MySQL(most versions) are both open source and
            > > provided free of charge. Presumably the dll included in the latest[/color][/color]
            builds[color=blue]
            > of[color=green]
            > > PHP5 is to ensure support for at least the free versions of MySQL is
            > > continued as before.[/color]
            >
            > Reminiscient of George Orwell's Animal Farm, some licenses are more "free"
            > than others. MySQL ships with a GPL license, which does not play nicely
            > with PHP's BSD-style license. (GPL would seem to imply that the simple[/color]
            act[color=blue]
            > of linking PHP to the MySQL client libraries would make PHP a derivative
            > work of MySQL... ya, okay.)
            >
            > Not all open-source projects are created equal. :-)
            >
            > For more information on the MySQL / PHP debundling and license issues,[/color]
            have[color=blue]
            > a look at http://www.phparch.com/mysql/
            >
            > HTH.
            > Pete.
            >
            > --
            > Peter James
            > petej@phparch.c om
            >
            > php|architect
            > The Magazine for PHP Professionals
            > http://www.phparch.com
            >
            >[/color]


            Comment

            • Mattiasz

              #7
              Re: PHP5 and MySQL

              I think no.


              Check out: http://www.nusphere.com/products/lib...401openmag.pdf
              (a lawyer's view on these matters)

              That being said, the Mysql license page contains some fuzzy-looking
              language to the effect that if your application can only use MySQL you
              may have to pay a license fee, but not if your application could
              (theoretically) use a different DB package. Sort of funny.

              Using PEAR DB, and staying away from MySQL-specific syntax should
              alleviate that concern, anyway.

              Best, Mattias



              Spidah wrote:
              [color=blue]
              > Exactly what does this mean for PHP scripters?
              >
              > If I write a PHP script that uses MySQL as its database engine is my script
              > considered a derivative work of MySQL (meaning I need a commercial MySQL
              > licence if I want to sell the script)?
              >
              > Regards
              > Hamilton
              >
              >
              > "Peter James" <petej@shaman.c a> wrote in message
              > news:vih7j0cg47 rs21@corp.super news.com...
              >[color=green][color=darkred]
              >>>Of course, I can't actually see how licensing issues would be behind the
              >>>change when both PHP & MySQL(most versions) are both open source and
              >>>provided free of charge. Presumably the dll included in the latest[/color][/color]
              >
              > builds
              >[color=green]
              >>of
              >>[color=darkred]
              >>>PHP5 is to ensure support for at least the free versions of MySQL is
              >>>continued as before.[/color]
              >>
              >>Reminiscien t of George Orwell's Animal Farm, some licenses are more "free"
              >>than others. MySQL ships with a GPL license, which does not play nicely
              >>with PHP's BSD-style license. (GPL would seem to imply that the simple[/color]
              >
              > act
              >[color=green]
              >>of linking PHP to the MySQL client libraries would make PHP a derivative
              >>work of MySQL... ya, okay.)
              >>
              >>Not all open-source projects are created equal. :-)
              >>
              >>For more information on the MySQL / PHP debundling and license issues,[/color]
              >
              > have
              >[color=green]
              >>a look at http://www.phparch.com/mysql/
              >>
              >>HTH.
              >>Pete.
              >>
              >>--
              >>Peter James
              >>petej@phparch .com
              >>
              >>php|archite ct
              >>The Magazine for PHP Professionals
              >>http://www.phparch.com
              >>
              >>[/color]
              >
              >
              >[/color]

              Comment

              Working...