Hi,
> http://wiki.php.net/rfc/namespaceissues
>
> Read it and discuss.
Solution #1 is imho the best one to disambiguate everything, but the
readability problem is not to be overlooked. To keep this short, just
read the following rewrite of the lines for the problem code:
foo.php
main.php
Hiyall,
> > So what is needed to get it on the pecl site in the packages list?
>
> 1) It needs to become registered as a package:
> http://pecl.php.net/package-new.php
>
> 2) In order to be downloadable it needs a release:
> http://pecl.php.net/release-upload.php
>
> For all of these steps you
Hiyall,
> Please note this: This was only removed from PHP 5.1-dev (HEAD),
> it still exists in the PHP_4_4 branch.. And AFAIK, there are no
> releases of PHP 5.1 (other than betas) out yet? :)
Still, some work needs to be done to make the transition to pecl
smoother, such as gett
Hiyall and Wez in particular,
> In general, unless the extension is a really ancient forgotten thing,
> the person moving it should coordinate with the current maintainer to
> set that up.
That would have been nice :-)
> Would you mind creating the appropriate package.xml file and tarball
> and
Hiyall,
A while back ext/dbx and ext/ircg were 'moved to pecl' (without any
discussion, but that's not the point).
However, there are no packages on pecl for either extension, which might
lead people to believe that a 'move to pecl' is more like a 'remove from
php' action. Should it not be polic
> > Doesn't ext/dbx already do what you're doing?
> John wrote ADOdb so he is looking to speed it up.
Which is funny, as I just wrote a pure-PHP version of ext/dbx for use in
environments where the C dbx extension is unavailable :-)
Cheerio, Marc.
--
PHP Internals - PHP Runtime Development Mai
Hi,
> I apologize for not going to the end of the thread to see if
> you posted a link online somewhere to this, but I would love
> a copy none the less.
It wasn't posted yet, but you can find it here:
http://www.guidance.nl/php/dbx/dbx.p
Cheerio, Marc.
--
PHP Internals - PHP Runtime Develop
Hi,
> i'll update the checkout on my server but you will have it through
> PECL anyway in a week.
I'll wait :-)
> > Great. What are the initial backends that will be supported? SQLite,
> > MySQL, PGSQL?
>
> SQLite and Oracle first. We're hoping that the exact two you mentioned
> follow very sh
Hi,
> I'm currently in DB API mode (working on PDO),
I know PDO is slated to be _the_ db-abstraction module from 5.x (5.1?)
onwards (which would replace dbx, but that's fine by me: PDO seems to
work more or less the same but with a more OO-ish api), but I was
wondering if these names bear any r
Hi,
> IMO there are some problems with the dbx extension:
>
> - it is a wrapper for PHP modules instead for the underlying
> database API (therefore slower)
True, but this makes for a lot less build-headaches: dbx has no
build-dependencies
> - you cannot rely on it if you depend on an ISP tha
Hi,
[Ard]
> First of all, in my opinion it would be more useful to concentrate on a
> true cross-database PHP-level data-object API which can really hide
> the differences between db implementations, instead of using the exact
> same function names, and ignoring the implementation differences
>
> that's the point. if the cracker can change only the end of
> the query, it's not so usefull for him (he can maximum get other id)
How about a form of dos:
'...where id = '.$id
with $id = '23129 or 1'
this will select all entries in the table which could result in DoS...
So, ultimately t
Hi,
the following script doesn't work correctly:
will produce
$ ./php -f sqlitetest.php
resource(1) of type (sqlite database (persistent))
resource(1) of type (Unknown)
This also happens if I call sqlite_close($handle) between the popens...
BTW, this is on the latest ext/sqlite copied to ex
13 matches
Mail list logo
