Am 31.03.2005 um 17:28 schrieb Marcus Boerger:
Hello Thies,
Friday, March 25, 2005, 1:55:30 PM, you wrote:
and this is 'cause pdo _expects_ the user to prefix the bound
variables
with a colon. grr...
ppls, lets change it before it's too late. this "tiny bit" makes
binding
harder than it should b
Yep, will do.
On Apr 1, 2005 3:13 AM, Thies C. Arntzen <[EMAIL PROTECTED]> wrote:
> so - again - lets make the colon *optional* - everywhere we allow
> binding in PDO!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
//Hi,//
//
//I am interested in contributing to PHP now that I have been using it
for 2 years or so. I was wondering how to get involved. I am not able to
help with the development of the language itself but I would be
interested in verifying bugs, writing documentation and/or maintaining
the w
David Mytton wrote:
> //Hi,//
> //
> //I am interested in contributing to PHP now that I have been using it
> for 2 years or so. I was wondering how to get involved. I am not able to
> help with the development of the language itself but I would be
> interested in verifying bugs, writing documentat
Hello Thies,
Friday, April 1, 2005, 3:13:10 AM, you wrote:
> Am 31.03.2005 um 17:28 schrieb Marcus Boerger:
>> Hello Thies,
>>
>> Friday, March 25, 2005, 1:55:30 PM, you wrote:
>>
>>> and this is 'cause pdo _expects_ the user to prefix the bound
>>> variables
>>> with a colon. grr...
>>
>>> pp
On Fri, 1 Apr 2005, Jason Barnett wrote:
> David Mytton wrote:
> > //Hi,//
> > //
> > //I am interested in contributing to PHP now that I have been using it
> > for 2 years or so. I was wondering how to get involved. I am not able to
> > help with the development of the language itself but I would
On Thu, Mar 31, 2005 at 04:50:22PM -0500,
Ilia Alshanetsky <[EMAIL PROTECTED]> is thought to have said:
> The PHP Development Team would like to announce the immediate release of
> PHP 4.3.11 and 5.0.4. These are maintenance releases that in addition
> to fixing over 70 non-critical bugs, addre
On Feb 27, 2005 8:19 AM, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> On Sun, 27 Feb 2005, Sebastian Bergmann wrote:
>
> > Jani Taskinen wrote:
> >> AC_MSG_WARN([You will need bison 1.28, 1.35, 1.75 or 1.875 if you want
> >
> > bison 2.0 also works (at least for me).
>
> Let's not add that to
Wez Furlong wrote:
Yep, will do.
I dont want to pretend that this change should open the flood gates for
radical changes. However there are still a few minor points beyond the
bindParam() that may need minor adjustments. Some of them can be added
later of course ..
1) DSN http://oss.backendmedi
Folks,
We have a bit of a situation with the PEAR distro that's embedded in
5.0.4. It's missing the RunTest.php file, so PEAR doesn't install.
The options we have, as far as I can tell, are:
[a] Re-release 5.0.4 with that file
[b] Release 5.0.5 with that file (seems a bit too aggressive consider
I
On Apr 1, 2005 5:00 PM, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> The options we have, as far as I can tell, are:
>
> [a] Re-release 5.0.4 with that file
> [b] Release 5.0.5 with that file (seems a bit too aggressive considering
> there are no code changes, and may cause confusion)
> [c] Instr
On Sat, 02 Apr 2005 00:00:18 +0200
[EMAIL PROTECTED] (Zeev Suraski) wrote:
> Folks,
>
> We have a bit of a situation with the PEAR distro that's embedded
> in 5.0.4. It's missing the RunTest.php file, so PEAR doesn't
> install.
>
> The options we have, as far as I can tell, are:
>
> [a] Re-re
Zeev Suraski wrote:
Folks,
We have a bit of a situation with the PEAR distro that's embedded in
5.0.4. It's missing the RunTest.php file, so PEAR doesn't install.
The options we have, as far as I can tell, are:
[a] Re-release 5.0.4 with that file
[b] Release 5.0.5 with that file (seems a bit too
Would 5.0.4pl1 be inappropriate?
Two different versions of 5.0.4 seems odd, and 5.0.5 seems too drastic as
you
mentioned. Otherwise, IMHO, just make a brief announcement, point them to
go-pear, and go through a normal 5.0.5 release cycle in a few weeks once a
few more fixes make it in.
Humbly, th
Option [a] seems like the most logical thing to do, would probably work the
best. It might be nice to note on php.net somewhere right now before this is
fixed that PEAR will not install.
The options we have, as far as I can tell, are:
[a] Re-release 5.0.4 with that file
[b] Release 5.0.5 with th
Hi
I think a 5.0.4.1 would be the best way to go (not sure what
versioning to use), as there are no real code changes to justify a
5.05. You could then provide a patch with notes for those with 5.04
installed or they could compile 5.0.4.1
I'd suggest if you rerelease the 5.0.4 as "5.0.4" then tho
On Fri, 1 Apr 2005, David Sklar wrote:
On Feb 27, 2005 8:19 AM, Jani Taskinen <[EMAIL PROTECTED]> wrote:
On Sun, 27 Feb 2005, Sebastian Bergmann wrote:
Jani Taskinen wrote:
AC_MSG_WARN([You will need bison 1.28, 1.35, 1.75 or 1.875 if you want
bison 2.0 also works (at least for me).
Let's not
17 matches
Mail list logo
