Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml pdo-stmt-t.xml preparation.xml prerequisites.xml
Philip Olson wrote: > 2. Discuss with the authors and IBM about transferring copyright You'll find this difficult, because there is no legal entity to which to transfer copyright. > The manual must not contain > copyrighted information from other parties and I am firm in this regard I think what you mean is that the manual must only contain content to which the PHP doc team *also* has copyright. There's plenty of material that belongs to others in the manual, but they have (implicitly) allowed that material to be used in the manual. > and already stated reasons why this is the case. Attribution yes, > copyright no. Again, what you really mean is that there cannot be material to which php-doc does not also have copyright. If you look at it in that light, there's really no reason why the other copyright holders can't also indicate that in the manual. Take a look in the PHP source; there's plenty of code in there that is copyrighted by others, but the content is under the PHP license. Translating that to the manual; the content is copyrighted by the authors, but the is under the OPL. Are your objections to copyright notices based on a legal notion, or on an aesthetic one? --Wez.
Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml pdo-stmt-t.xml preparation.xml prerequisites.xml
Philip Olson wrote: > It's easy to say "credit everyone" but implementing this in a fair, I think you'll find that I didn't say that here. > The removed text in those PDO docs did not follow the guidelines so it > was a bug. Attribution is a bug!? > Nowhere else does text exist like this so what makes the PDO > HOWTO so special? I think this is one of the first cases where an external entity has contributed a significant portion of text to the manual, and that that has coincided with the people involved actually knowing how to correctly express authorship using docbook. > If a person and/or company absolutely insists on > inserting copyright/author information into a file then they need not > commit it to the phpdoc CVS module because nobody deserves special > treatment or owns certain text in the manual. Actually, those people do own the copyright on their contributions to the manual, and I think (IANAL), that they are legally allowed to indicate that. > Bill and Rick have now appropriately been > added to the contributors list, a list that Wez is already on. Did you also add IBM to that list? They are a copyright holder too. Just to be clear, I didn't even notice that my name was one of those removed. I don't particularly care where my name is in the manual; I'm reacting in this thread because I firmly believe that two of the most disrespectful things that one can do to a open contributor is take their work without giving credit, and to remove attribution from their work. I suspect that Bill and Rick would not have found their way into the contributors list if I hadn't gotten involved. I also find the attitude expressed above about making contributions to be a practical blocker for anyone adding any substantial text in the future, and personally find it insulting. I don't mean to come across all high-and-mighty, or holier-than-thou, but I want to let you know that I feel very strongly that php-doc is moving in the wrong direction here. I'm bowing out from php-doc now. I enjoyed contributing what I did, but don't think it will be the same going forward. If I might suggest one last thing before I depart; on a technical level, docbook is designed to hold information in a structured and parseable format. I recommend that you use it to retain authorship information and customize the XSL to prevent it from appearing in the online manual, if that really is how you want to do things moving forward. --Wez.
Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml pdo-stmt-t.xml preparation.xml prerequisites.xml
You already know my views on this ridiculous scheme (for the others listening in, search the archives for penis comparison). As for community needs, nobody in the community needs these authors names removed from the text, but on the other hand, the community does need documentation. There was nothing wrong with putting correct attribution in the text, so there is no reason to remove it now. In fact, it's a big f-you to those people. I strongly recommend that you put their names back. If you insist on removing good documentation over this retarded ideal, so be it, but don't expect me to contribute any further, nor to have me recommend anyone else waste their time either. --Wez. Philip Olson wrote: > > Hello Wez- > > The PHP manual does not insert author and company names like this and I > encouraged Gwynne to remove these attributions. We're researching a > method for crediting "sponsored" documentation but they should not be > treated in a special manner... all contributors and contributions should > be treated the same. In fact, the entire credits system (a topic that is > just about impossible to maintain) is being reevaluated at this time. > > The text did say we can "edit, combine, transform, rewrite, etc. as > suits the needs of the community" and the community does not write > credits like that nor does a commit imply that credits will be added > outside the CVS changelog. I am not prepared to discuss the credit > system as a whole but in time it will happen. If you/they require that > information to remain as is then I'd rather remove the docs and move on > but I doubt it will come to that. The work is appreciated but we must > remain fair and consistent and encourage everyone to feel free to edit > any and all documentation in the manual and never worry about when or > when not to add a persons name. > > Regards, > Philip > > On Jun 6, 2007, at 6:13 AM, Wez Furlong wrote: > >> Please put the attribution back, as a matter of courtesy to those >> authors efforts as they kindly donated those docs and don't otherwise >> have any way of being credited for their work. >> >> --Wez. >> >> PS: As a general rule of thumb, never remove any attribution, license or >> copyright information from a file unless you are 100% certain that it no >> longer applies. >> >> >> Buesching, Logan J wrote: >>> I thought all the docs we have and create were under an open license? >>> >>> >>> >>> From: Nuno Lopes [mailto:[EMAIL PROTECTED] >>> Sent: Wed 6/6/2007 8:32 AM >>> To: Gwynne Amaya Raskind >>> Cc: PHPdoc; [EMAIL PROTECTED] >>> Subject: Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml >>> error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml >>> pdo-stmt-t.xml preparation.xml prerequisites.xml >>> >>> >>> >>>> gwynne Wed Jun 6 05:20:48 2007 UTC >>>> >>>> Modified files: >>>>/phpdoc/en/internals/pdo building.xml error-handling.xml >>>>implementing.xml index.xml intro.xml >>>>pdo-dbh-t.xml pdo-stmt-t.xml >>>>preparation.xml prerequisites.xml >>>> Log: >>>> - Fixed several spelling and grammatical errors in the PDO >>>> documentation. >>>> - Removed displayed author information from the PDO documentation >>>> front >>>> page. >>> >>> I don't know if that is legal. You need to check out what was the >>> agreement >>> with IBM for distribution of those docs. Maybe Wez can help on this >>> subject? >>> >>> Nuno >>> >>> >>> >>
Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml pdo-stmt-t.xml preparation.xml prerequisites.xml
Please put the attribution back, as a matter of courtesy to those authors efforts as they kindly donated those docs and don't otherwise have any way of being credited for their work. --Wez. PS: As a general rule of thumb, never remove any attribution, license or copyright information from a file unless you are 100% certain that it no longer applies. Buesching, Logan J wrote: > I thought all the docs we have and create were under an open license? > > > > From: Nuno Lopes [mailto:[EMAIL PROTECTED] > Sent: Wed 6/6/2007 8:32 AM > To: Gwynne Amaya Raskind > Cc: PHPdoc; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] cvs: phpdoc /en/internals/pdo building.xml > error-handling.xml implementing.xml index.xml intro.xml pdo-dbh-t.xml > pdo-stmt-t.xml preparation.xml prerequisites.xml > > > >> gwynne Wed Jun 6 05:20:48 2007 UTC >> >> Modified files: >>/phpdoc/en/internals/pdo building.xml error-handling.xml >>implementing.xml index.xml intro.xml >>pdo-dbh-t.xml pdo-stmt-t.xml >>preparation.xml prerequisites.xml >> Log: >> - Fixed several spelling and grammatical errors in the PDO documentation. >> - Removed displayed author information from the PDO documentation front >> page. > > I don't know if that is legal. You need to check out what was the agreement > with IBM for distribution of those docs. Maybe Wez can help on this subject? > > Nuno > > >
[PHP-DOC] cvs: php-src(PHP_5_2) / NEWS /ext/pdo_sqlite config.w32
wez Thu Mar 22 01:00:23 2007 UTC
Modified files: (Branch: PHP_5_2)
/php-srcNEWS
/php-src/ext/pdo_sqlite config.w32
Log:
Add php_pdo_sqlite_external.dll to windows build.
This allows the user to provide their own version of sqlite3.dll.
The php_pdo_sqlite.dll is still there, and will continue to be there.
It is built from the bundled sources.
[[DOC]]
(this should cc: phpdoc, if it's wrong, please let the docs folks know :-)
http://cvs.php.net/viewvc.cgi/php-src/NEWS?r1=1.2027.2.547.2.608&r2=1.2027.2.547.2.609&diff_format=u
Index: php-src/NEWS
diff -u php-src/NEWS:1.2027.2.547.2.608 php-src/NEWS:1.2027.2.547.2.609
--- php-src/NEWS:1.2027.2.547.2.608 Wed Mar 21 00:25:43 2007
+++ php-src/NEWSThu Mar 22 01:00:23 2007
@@ -23,6 +23,9 @@
- Added tidyNode::getParent() method (John, Nuno)
- Added openbasedir and safemode checks in zip:// stream wrapper and
ZipArchive::open (Pierre)
+- Added php_pdo_sqlite_external.dll, a version of the PDO SQLite driver that
+ links against an external sqlite3.dll. This provides Windows users to
upgrade
+ their sqlite3 version outside of the PHP release cycle. (Wez, Edin)
- Fixed shmop_open() with IPC_CREAT|IPC_EXCL flags on Windows.
(Vladimir Kamaev, Tony).
- Fixed possible leak in ZipArchive::extractTo when safemode checks fails
(Ilia)
http://cvs.php.net/viewvc.cgi/php-src/ext/pdo_sqlite/config.w32?r1=1.6.2.1.2.2&r2=1.6.2.1.2.3&diff_format=u
Index: php-src/ext/pdo_sqlite/config.w32
diff -u php-src/ext/pdo_sqlite/config.w32:1.6.2.1.2.2
php-src/ext/pdo_sqlite/config.w32:1.6.2.1.2.3
--- php-src/ext/pdo_sqlite/config.w32:1.6.2.1.2.2 Mon Aug 14 16:15:28 2006
+++ php-src/ext/pdo_sqlite/config.w32 Thu Mar 22 01:00:23 2007
@@ -1,4 +1,4 @@
-// $Id: config.w32,v 1.6.2.1.2.2 2006/08/14 16:15:28 iliaa Exp $
+// $Id: config.w32,v 1.6.2.1.2.3 2007/03/22 01:00:23 wez Exp $
// vim:ft=javascript
ARG_WITH("pdo-sqlite", "for pdo_sqlite support", "no");
@@ -29,3 +29,10 @@
ADD_EXTENSION_DEP('pdo_sqlite', 'pdo');
}
+ARG_WITH("pdo-sqlite-external", "for pdo_sqlite support from an external dll",
"no");
+if (PHP_PDO_SQLITE_EXTERNAL != "no") {
+ CHECK_HEADER_ADD_INCLUDE("sqlite3.h", "CFLAGS_PDO_SQLITE_EXTERNAL",
PHP_PDO_SQLITE_EXTERNAL + ";" + PHP_PHP_BUILD + "\\include\\sqlite3");
+ CHECK_LIB("sqlite3-import.lib", "pdo_sqlite_external",
PHP_PDO_SQLITE_EXTERNAL + ";" + PHP_PHP_BUILD + "\\lib");
+ EXTENSION("pdo_sqlite_external", "pdo_sqlite.c sqlite_driver.c
sqlite_statement.c", null, "/I" + configure_module_dirname, null,
"ext\\pdo_sqlite_external");
+ ADD_EXTENSION_DEP('pdo_sqlite_external', 'pdo');
+}
Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Improving the documentation
I tweaked loginfo.pl so that if the commit message contains [DOC], phpdoc@ will be Cc'd. Hopefully that'll help in some small way. --Wez. On 2/10/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote: We, and by we I mean all of us who write code and hope that divine intervention will take care of the documentation, need to do a better job helping out divinity. A DOC tag in cvs commit messages seems like a small and easy thing for us to add to the process, so if you feel that will be enough to make things easier, let's do that. Perhaps we can do more though. Maybe you guys could periodically update internals on problem areas in the docs. Places where you feel things are vague and really could use the guy who wrote the code to get off his ass and explain how it works. Or maybe we could get everyone who reads internals to pick a page or two in the manual on something they are intimately familiar with and go over it in detail and feed suggestions back to phpdoc@ -Rasmus Ronald Chmara wrote: > On Jan 27, 2007, at 8:26 AM, Mehdi Achour wrote: >> Hello internals, >> I've been helping with PHP documentation for 4 years now, and I still >> can't help the fact that a lt of things are not documented, that >> our/my way of handling the PHP documentation update is not accurate, >> nor productive, nor bug free at all. > > I think it's been ~7 years of off and on work for me... same as it ever > was. I do think it's *much* more productive and accurate than it was 7 > years ago, though. Not quite bug-free, yet. > > (You think it's bad now...) > >> Personally, I try to follow commits on php.cvs, bug reports, Change >> Log?, user notes on the online manual.. but I still have the feeling >> of missing a lot of changes. After a year away from the project, I >> have _no_ clue what was added, when, and whether it was added to our >> documentation or not. > > You are in the same boat as me. The dunes change, but the sands are > always shifting. I might have been away for n years. Much has changed, > and much has not. > >> I know that you developers are willing to help a lot with it, but that >> you cannot manage to save the spare time needed to do it the right >> way. That's why I would like to propose a simple/small/timeless change >> in your CVS commit messages: If you feel that the change need to be >> documented, place the @doc keyword at the end of your message log entry. > > Scenario one: > All behavior changes must be documented, this tag is always there, and > thus not useful. > > Scenario two: > Developers decide when changes are "important" enough to be documented, > and tag as such, in which case we go back to... > > Scenario three: > The problem of developers who don't think documentation is needed for > their changes. > > In the end, I often wonder if this is documentation issue, or a > developer issue. Developers read the code, and often don't need *any* > documentation. Our end users read a manual page, and wonder what a > "bool" or "int" is, as a very large number of our users are fairly new > to the whole subject matter. > > (side joke, does PHP have a zool(), destroyer of all world (global) > variables?) > > Anyways, to me, the real challenge of working on the PHP docs is not > getting programmers to feed us reliable, consistent, data all the time > (they won't), but rather, helping out our end users who don't read > source code. > > Vanity devs will want us to document everything, quiet devs will never > tag it. > > In the end, the doc team still has to fix it. > > -Ronabop > > --PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] cvs: phpdoc /en/appendices wrappers.xml
wez Sat Oct 21 22:45:08 2006 UTC Modified files: /phpdoc/en/appendices wrappers.xml Log: add note about open/close semantics for php://stdin and friends http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/wrappers.xml?r1=1.65&r2=1.66&diff_format=u Index: phpdoc/en/appendices/wrappers.xml diff -u phpdoc/en/appendices/wrappers.xml:1.65 phpdoc/en/appendices/wrappers.xml:1.66 --- phpdoc/en/appendices/wrappers.xml:1.65 Fri Sep 22 17:05:11 2006 +++ phpdoc/en/appendices/wrappers.xml Sat Oct 21 22:45:08 2006 @@ -1,5 +1,5 @@ - + List of Supported Protocols/Wrappers @@ -618,7 +618,15 @@ php://stdin, php://stdout and php://stderr allow access to - the corresponding input or output stream of the PHP process. + the corresponding input or output stream of the PHP process. The stream + references a duplicate file descriptor, so if you open + php://stdin and later close it, you close only your + copy of the descriptor--the actual stream referenced by + STDIN is unaffected. Note that PHP exhibited buggy + behavior in this regard until PHP 5.2.1. It is recommended that you simply + use the constants STDIN, STDOUT + and STDERR instead of manually opening streams using + these wrappers. php://output allows you to write to the
[PHP-DOC] Re: CHM build machine - Was[2]: [PHP-DOC] #34026 [Ver->Opn]: Polish CHM is corrupted
I now have a box and I'm waiting for the OS and other tools for it to arrive; given how busy things are, it'll be a few weeks before its fully operational. --Wez. techtonik wrote: > Any progress? I noticed that CHM file dates are new, but I can't say > if build process takes place, because Polish CHM is still corrupted > and it's size still 400Kb against usual 6Mb > http://www.php.net/download-docs.php?sizes=1 > http://bugs.php.net/bug.php?id=34026 > > If something touches files even if the build fails - it is a bad U > problem (by FUD classification). > > On 5/2/06, Wez Furlong wrote: >> We're supposed to getting donated a windows build box for this kind of >> thing; I'll chase up my contacts to see when that will be. >> >> --Wez. >> >> anatoly techtonik wrote: >> > As far as I can understand the problem on the surface is in windows >> > machine where hhc.exe needs to be executed. As the windows machine >> > is not available for PHP folks at http://master.php.net/inventory.php >> > we have to use somebody's private host to compile .chm's >> > >
[PHP-DOC] Re: CHM build machine - Was[2]: [PHP-DOC] #34026 [Ver->Opn]: Polish CHM is corrupted
We're supposed to getting donated a windows build box for this kind of thing; I'll chase up my contacts to see when that will be. --Wez. anatoly techtonik wrote: > As far as I can understand the problem on the surface is in windows > machine where hhc.exe needs to be executed. As the windows machine > is not available for PHP folks at http://master.php.net/inventory.php > we have to use somebody's private host to compile .chm's
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-query.xml PDOStatement-setFetchMode.xml
wez Sun Apr 30 02:39:22 2006 UTC Modified files: /phpdoc/en/reference/pdo/functions PDO-query.xml PDOStatement-setFetchMode.xml Log: improve documentation on PDOStatement::setFetchMode() and PDO::query(). http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/pdo/functions/PDO-query.xml?r1=1.6&r2=1.7&diff_format=u Index: phpdoc/en/reference/pdo/functions/PDO-query.xml diff -u phpdoc/en/reference/pdo/functions/PDO-query.xml:1.6 phpdoc/en/reference/pdo/functions/PDO-query.xml:1.7 --- phpdoc/en/reference/pdo/functions/PDO-query.xml:1.6 Wed Oct 19 20:45:02 2005 +++ phpdoc/en/reference/pdo/functions/PDO-query.xml Sun Apr 30 02:39:21 2006 @@ -1,5 +1,5 @@ - + @@ -15,6 +15,28 @@ stringstatement + + boolPDO::query + stringstatement + intPDO::FETCH_COLUMN + intcolno + + + + boolPDO::query + stringstatement + intPDO::FETCH_CLASS + stringclassname + arrayctorargs + + + + boolPDO::query + stringstatement + intPDO::FETCH_INTO + objectobject + + PDO::query executes an SQL statement in a single function call, returning the result set (if any) returned by the @@ -34,6 +56,16 @@ next call to PDO::query. + + +Although this function is only documented as having a single +parameter, you may pass additional arguments to this function. +They will be treated as though you called +PDOStatement::setFetchMode on the resultant statement +object. + + + &reftitle.parameters; http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml?r1=1.4&r2=1.5&diff_format=u Index: phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml diff -u phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml:1.4 phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml:1.5 --- phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml:1.4 Tue Sep 20 08:22:29 2005 +++ phpdoc/en/reference/pdo/functions/PDOStatement-setFetchMode.xml Sun Apr 30 02:39:22 2006 @@ -1,5 +1,5 @@ - + @@ -15,6 +15,25 @@ intmode + + boolPDOStatement::setFetchMode + intPDO::FETCH_COLUMN + intcolno + + + + boolPDOStatement::setFetchMode + intPDO::FETCH_CLASS + stringclassname + arrayctorargs + + + + boolPDOStatement::setFetchMode + intPDO::FETCH_INTO + objectobject + + &reftitle.parameters;
[PHP-DOC] cvs: phpdoc /en/reference/pdo_mysql constants.xml
wez Thu Mar 30 14:33:55 2006 UTC Modified files: /phpdoc/en/reference/pdo_mysql constants.xml Log: fix constant names http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/pdo_mysql/constants.xml?r1=1.3&r2=1.4&diff_format=u Index: phpdoc/en/reference/pdo_mysql/constants.xml diff -u phpdoc/en/reference/pdo_mysql/constants.xml:1.3 phpdoc/en/reference/pdo_mysql/constants.xml:1.4 --- phpdoc/en/reference/pdo_mysql/constants.xml:1.3 Fri Nov 18 16:25:23 2005 +++ phpdoc/en/reference/pdo_mysql/constants.xml Thu Mar 30 14:33:55 2006 @@ -1,12 +1,12 @@ - + &reftitle.constants; &pdo.driver-constants; -PDO_MYSQL_ATTR_USE_BUFFERED_QUERY +PDO::MYSQL_ATTR_USE_BUFFERED_QUERY (integer) @@ -21,9 +21,9 @@
[PHP-DOC] cvs: phpdoc /en/reference/pdo_pgsql/functions PDO-pgsqlLOBCreate.xml PDO-pgsqlLOBOpen.xml PDO-pgsqlLOBUnlink.xml
wez Mon Nov 28 23:07:04 2005 EDT Added files: /phpdoc/en/reference/pdo_pgsql/functionsPDO-pgsqlLOBCreate.xml PDO-pgsqlLOBOpen.xml PDO-pgsqlLOBUnlink.xml Log: Document new lob functions http://cvs.php.net/co.php/phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBCreate.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBCreate.xml +++ phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBCreate.xml PDO::pgsqlLOBCreate Creates a new large object, returning its identifier. Must be called inside a transaction. &reftitle.description; stringPDO::pgsqlLOBCreate PDO::pgsqlLOBCreate creates a large object and returns the OID of that object. You may then open a stream on the object using PDO::pgsqlLOBOpen to read or write data to it. The OID can be stored in columns of type OID and be used to reference the large object, without causing the row to grow arbitrarily large. The large object will continue to live in the database until it is removed by calling PDO::pgsqlLOBUnlink. Large objects can be up to 2GB in size, but are cumbersome to use; you need to ensure that PDO::pgsqlLOBUnlink is called prior to deleting the last row that references its OID from your database. In addition, large objects have no access controls. As an alternative, try the bytea column type; recent versions of PostgreSQL allow bytea columns of up to 1GB in size and transparently manage the storage for optimal row size. This function must be called within a transaction. &reftitle.parameters; PDO::pgsqlLOBCreate takes no parameters. &reftitle.returnvalues; Returns the OID of the newly created large object on success, or &false; on failure. &reftitle.examples; A PDO::pgsqlLOBCreate example This example creates a new large object and copies the contents of a file into it. The OID is then stored into a table. &reftitle.seealso; PDO::pgsqlLOBOpen PDO::pgsqlLOBCreate pg_lo_create http://cvs.php.net/co.php/phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBOpen.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBOpen.xml +++ phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBOpen.xml PDO::pgsqlLOBOpen Opens an existing large object stream. Must be called inside a transaction. &reftitle.description; resourcePDO::pgsqlLOBOpen stringoid stringmode PDO::pgsqlLOBOpen opens a stream to access the data referenced by oid. If mode is r, the stream is opened for reading, if mode is w, then the stream will be opened for writing. You can use all the usual filesystem functions, such as fread, fwrite and fgets to manipulate the contents of the stream. This function, and all manipulations of the large object, must be called and carried out within a transaction. &reftitle.parameters; oid A large object identifier. mode If mode is r, open the stream for reading. If mode is w, open the stream for writing. &reftitle.returnvalues; Returns a stream resource on success, of &false; on failure. &reftitle.examples; A PDO::pgsqlLOBOpen example Following on from the PDO::pgsqlLOBCreate example, this code snippet retrieves the large object from the database and outputs it to the browser. &reftitle.seealso; PDO::pgsqlLOBCreate PDO::pgsqlLOBUnlink pg_lo_open http://cvs.php.net/co.php/phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBUnlink.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBUnlink.xml +++ phpdoc/en/reference/pdo_pgsql/functions/PDO-pgsqlLOBUnlink.xml PDO::pgsqlLOBUnlink Deletes the large object identified by oid. Must be called inside a transaction. &reftitle.description; boolPDO::pgsqlLOBUnlink stringoid Deletes a large object from the database. This function must be called within a transaction. &reftitle.parameters; oid The large object identifier &reftitle.returnvalues; &return.success; &reftitle.examples; A PDO::pgsqlLOBUnlink example This example unlinks a large object from the database prior to deleting the row that references it from the blobs table we've been using in our PDO::pgsqlLOBCreate and PDO::pgsqlLOBOpen examples. &reftitle.seealso; PDO::pgsqlLOBOpen PDO::pgsql
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
Yep. And in reply to your comment on my blog, getColumnMeta is the only experimental API; I've already marked up the docs appropriately... except for this comment. --Wez. On 11/28/05, Jakub Vrana <[EMAIL PROTECTED]> wrote: > vrana Mon Nov 28 04:24:49 2005 EDT > > Modified files: > /phpdoc/en/reference/pdoreference.xml > Log: > Wez says that PDO is no more experimental > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.44&r2=1.45&ty=u > Index: phpdoc/en/reference/pdo/reference.xml > diff -u phpdoc/en/reference/pdo/reference.xml:1.44 > phpdoc/en/reference/pdo/reference.xml:1.45 > --- phpdoc/en/reference/pdo/reference.xml:1.44 Sun Oct 30 22:06:55 2005 > +++ phpdoc/en/reference/pdo/reference.xml Mon Nov 28 04:24:46 2005 > @@ -1,8 +1,7 @@ > > - > + > > > - > > >PDO Functions >
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml
wez Thu Nov 24 16:46:10 2005 EDT Modified files: /phpdoc/en/reference/pdoconstants.xml Log: PDO::FETCH_CLASSTYPE is an internal constant flag http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.12&r2=1.13&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.12 phpdoc/en/reference/pdo/constants.xml:1.13 --- phpdoc/en/reference/pdo/constants.xml:1.12 Tue Sep 20 04:22:28 2005 +++ phpdoc/en/reference/pdo/constants.xml Thu Nov 24 16:46:08 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -256,17 +256,6 @@ -PDO::FETCH_CLASSTYPE - (integer) - - - - - - - - - PDO::ATTR_AUTOCOMMIT (integer)
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-quote.xml
wez Thu Nov 24 14:05:49 2005 EDT Modified files: /phpdoc/en/reference/pdo/functions PDO-quote.xml Log: tweak http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-quote.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-quote.xml diff -u phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.5 phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.6 --- phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.5 Thu Oct 20 16:29:47 2005 +++ phpdoc/en/reference/pdo/functions/PDO-quote.xml Thu Nov 24 14:05:47 2005 @@ -1,5 +1,5 @@ - + @@ -17,8 +17,8 @@ - PDO::quote places quotes around the input - string and escapes and single quotes within the input string, using a + PDO::quote places quotes around the input string (if + required) and escapes special characters within the input string, using a quoting style appropriate to the underlying driver. @@ -26,10 +26,10 @@ strongly recommended to use PDO::prepare to prepare SQL statements with bound parameters instead of using PDO::quote to interpolate - user input into a SQL statement. Prepared statements with bound parameters - are not only more portable, more convenient, and vastly more secure, but - are often much faster than interpolating user input into slight variations - on the same basic SQL statement. + user input into a SQL statement. Prepared statements with bound parameters + are not only more portable, more convenient, immune to SQL injection, but + are often much faster to execute than interpolated queries, as both the + server and client side can cache a compiled form of the query. Not all PDO drivers implement this method (notably PDO_ODBC). Consider
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-getAttribute.xml PDO-setAttribute.xml PDOStatement-getAttribute.xml PDOStatement-setAttribute.xml
The attribute is handled implicitly at prepare time (which is the only
portable way to set this attribute).
--Wez.
On 11/3/05, Jakub Vrana <[EMAIL PROTECTED]> wrote:
> Wez Furlong wrote:
> > Err, this isn't firebird specific; it's also used for postgres and
> > odbc, and can be used to set and get the cursor name for "UPDATE ...
> > WHERE CURRENT OF ... " queries.
>
> Thanks for pointing. I found it in ODBC but couldn't find it in
> Postgres:
>
> > struct pdo_stmt_methods pgsql_stmt_methods = {
> ...
> > NULL, /* set_attr */
> > NULL, /* get_attr */
>
> Jakub Vrana
>
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-getAttribute.xml PDO-setAttribute.xml PDOStatement-getAttribute.xml PDOStatement-setAttribute.xml
An attribute is only driver specific if the constant name has the driver name in it. --Wez. On 11/3/05, Wez Furlong <[EMAIL PROTECTED]> wrote: > Err, this isn't firebird specific; it's also used for postgres and > odbc, and can be used to set and get the cursor name for "UPDATE ... > WHERE CURRENT OF ... " queries. > > --Wez. > > On 11/2/05, Jakub Vrana <[EMAIL PROTECTED]> wrote: > > - &warn.undocumented.func; > > + > > + Gets an attribute of the statement. Currently, no generic attributes > > exist but only driver specific: > > + > > +PDO::ATTR_CURSOR_NAME (Firebird > > specific): > > + Get the name of cursor. > > + > > + > > + > > >
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-getAttribute.xml PDO-setAttribute.xml PDOStatement-getAttribute.xml PDOStatement-setAttribute.xml
Err, this isn't firebird specific; it's also used for postgres and odbc, and can be used to set and get the cursor name for "UPDATE ... WHERE CURRENT OF ... " queries. --Wez. On 11/2/05, Jakub Vrana <[EMAIL PROTECTED]> wrote: > - &warn.undocumented.func; > + > + Gets an attribute of the statement. Currently, no generic attributes > exist but only driver specific: > + > +PDO::ATTR_CURSOR_NAME (Firebird > specific): > + Get the name of cursor. > + > + > + >
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sun Oct 30 22:06:57 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: update for oracle LOB support http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.43&r2=1.44&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.43 phpdoc/en/reference/pdo/reference.xml:1.44 --- phpdoc/en/reference/pdo/reference.xml:1.43 Mon Oct 17 23:20:13 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Oct 30 22:06:55 2005 @@ -1,5 +1,5 @@ - + @@ -751,12 +751,49 @@ $stmt->bindParam(2, $_FILES['file']['type']); $stmt->bindParam(3, $fp, PDO::PARAM_LOB); +$stmt->beginTransaction(); $stmt->execute(); +$stmt->commit(); +?> +]]> + + + + +Inserting an image into a database: Oracle + + Oracle requires a slightly different syntax for inserting a lob from a + file. It's also essential that you perform the insert under a + transaction, otherwise your newly inserted LOB will be committed with a + zero-length as part of the implicit commit that happens when the query + is executed: + + + +
[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions fread.xml
wez Thu Oct 27 16:31:19 2005 EDT Modified files: /phpdoc/en/reference/filesystem/functions fread.xml Log: clarify that greedy read is for regular local files only. http://cvs.php.net/diff.php/phpdoc/en/reference/filesystem/functions/fread.xml?r1=1.17&r2=1.18&ty=u Index: phpdoc/en/reference/filesystem/functions/fread.xml diff -u phpdoc/en/reference/filesystem/functions/fread.xml:1.17 phpdoc/en/reference/filesystem/functions/fread.xml:1.18 --- phpdoc/en/reference/filesystem/functions/fread.xml:1.17 Fri Oct 14 04:56:55 2005 +++ phpdoc/en/reference/filesystem/functions/fread.xml Thu Oct 27 16:31:18 2005 @@ -1,5 +1,5 @@ - + @@ -16,7 +16,7 @@ fread reads up to length bytes from the file pointer - referenced by handle. Reading stops when + referenced by handle. Reading stops when up to length bytes have been read, EOF (end of file) is reached, or (for network streams) when a packet becomes available, whichever comes first. @@ -63,11 +63,12 @@ - When reading from network streams or pipes, such as those returned when + When reading from anything that is not a regular local file, such as + streams returned when reading remote files or from popen and fsockopen, reading will stop after a packet is available. This means that you should - collect the data together in chunks as shown in the example below. + collect the data together in chunks as shown in the examples below. @@ -75,6 +76,20 @@ + + + + + + +
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
"Now that you're connected via PDO, you should understand how PDO" was what I intended that to say :) --Wez. On 10/17/05, Dan Scott <[EMAIL PROTECTED]> wrote: > dbs Mon Oct 17 16:23:45 2005 EDT > > Modified files: > /phpdoc/en/reference/pdoreference.xml > Log: > Correct typo reported in bug #34897. > > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.41&r2=1.42&ty=u > Index: phpdoc/en/reference/pdo/reference.xml > diff -u phpdoc/en/reference/pdo/reference.xml:1.41 > phpdoc/en/reference/pdo/reference.xml:1.42 > --- phpdoc/en/reference/pdo/reference.xml:1.41 Sat Sep 24 11:51:16 2005 > +++ phpdoc/en/reference/pdo/reference.xml Mon Oct 17 16:23:43 2005 > @@ -1,5 +1,5 @@ > > - > + > > > > @@ -347,7 +347,7 @@ > > Transactions and auto-commit > > - Now that you're connected via PDO, you should to understand how PDO > + Now that you're connected via PDO, you should be able to understand how > PDO > manages transactions before you start issuing queries. If you've never > encountered transactions before, they offer 4 major features: Atomicity, > Consistency, Isolation and Durability (ACID). In layman's terms, any > work >
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sat Sep 24 11:51:17 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: a note about catching exceptions and the dangers of not doing so on a production site. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.40&r2=1.41&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.40 phpdoc/en/reference/pdo/reference.xml:1.41 --- phpdoc/en/reference/pdo/reference.xml:1.40 Tue Sep 20 04:22:28 2005 +++ phpdoc/en/reference/pdo/reference.xml Sat Sep 24 11:51:16 2005 @@ -1,5 +1,5 @@ - + @@ -271,6 +271,17 @@ + + + If your application does not catch the exception thrown from the PDO + constructor, the default action taken by the zend engine is to terminate + the script and display a back trace. This back trace will likely reveal + the full database connection details, including the username and + password. It is your responsibility to catch this exception, either + explicitly (via a catch statement) or implicitly via + set_exception_handler. + + Upon successful connection to the database, an instance of the PDO class is returned to your script. The connection remains active for the
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-getAvailableDrivers.xml pdo-drivers.xml
wez Sun Sep 18 10:17:32 2005 EDT Added files: /phpdoc/en/reference/pdo/functions PDO-getAvailableDrivers.xml Removed files: /phpdoc/en/reference/pdo/functions pdo-drivers.xml Log: rename pdo_drivers() to PDO::getAvailableDrivers as part of namespacing sweep before 1.0 stable. http://cvs.php.net/co.php/phpdoc/en/reference/pdo/functions/PDO-getAvailableDrivers.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo/functions/PDO-getAvailableDrivers.xml +++ phpdoc/en/reference/pdo/functions/PDO-getAvailableDrivers.xml PDO::getAvailableDrivers Return an array of available PDO drivers &reftitle.description; arrayPDO::getAvailableDrivers This function returns all currently available PDO drivers which can be used in DSN parameter of PDO::__construct. This is a static method. &reftitle.returnvalues; PDO::getAvailableDrivers returns an array of PDO driver names. If no drivers are available, it returns an empty array. &reftitle.examples; A PDO::getAvailableDrivers example &example.outputs.similar;
[PHP-DOC] cvs: phpdoc /en/reference/pdo_sqlite reference.xml
wez Sun Sep 18 10:06:34 2005 EDT Modified files: /phpdoc/en/reference/pdo_sqlite reference.xml Log: not really experimental any more http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/reference.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/reference/pdo_sqlite/reference.xml diff -u phpdoc/en/reference/pdo_sqlite/reference.xml:1.8 phpdoc/en/reference/pdo_sqlite/reference.xml:1.9 --- phpdoc/en/reference/pdo_sqlite/reference.xml:1.8Sun Sep 11 02:17:09 2005 +++ phpdoc/en/reference/pdo_sqlite/reference.xmlSun Sep 18 10:06:34 2005 @@ -1,5 +1,5 @@ - + @@ -11,7 +11,6 @@ &reftitle.intro; - &warn.experimental; PDO_SQLITE is a driver that implements the PHP Data Objects (PDO) interface to enable access to SQLite 3 databases.
[PHP-DOC] cvs: livedocs / mkindex.php
wez Sun Sep 18 10:04:28 2005 EDT
Modified files:
/livedocs mkindex.php
Log:
ignore all files beginning with a ., and not just the magic dirs.
rationale: no point trying to index vim .swp files, as that just confuses
things.
http://cvs.php.net/diff.php/livedocs/mkindex.php?r1=1.46&r2=1.47&ty=u
Index: livedocs/mkindex.php
diff -u livedocs/mkindex.php:1.46 livedocs/mkindex.php:1.47
--- livedocs/mkindex.php:1.46 Sat Aug 20 17:50:38 2005
+++ livedocs/mkindex.phpSun Sep 18 10:04:27 2005
@@ -19,7 +19,7 @@
// | construct an index |
// +--+
//
-// $Id: mkindex.php,v 1.46 2005/08/20 21:50:38 edink Exp $
+// $Id: mkindex.php,v 1.47 2005/09/18 14:04:27 wez Exp $
/* just to be on the safe side */
@@ -319,7 +319,7 @@
}
while (($f = readdir($d)) !== false) {
- if ($f == 'CVS' || $f == '.' || $f == '..') {
+ if ($f == 'CVS' || $f{0} == '.') {
continue;
}
$full = $dirname . DIRECTORY_SEPARATOR . $f;
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml reference.xml
wez Sun Sep 18 10:03:32 2005 EDT Modified files: /phpdoc/en/reference/pdoconstants.xml reference.xml Log: flesh out some more http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.10&r2=1.11&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.10 phpdoc/en/reference/pdo/constants.xml:1.11 --- phpdoc/en/reference/pdo/constants.xml:1.10 Thu Sep 15 16:57:50 2005 +++ phpdoc/en/reference/pdo/constants.xml Sun Sep 18 10:03:30 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -68,7 +68,7 @@ - + Represents a recordset type. Not currently supported by any drivers. @@ -280,7 +280,8 @@ Setting the prefetch size allows you to balance speed against memory usage for your application. Not all database/driver combinations support - setting of the prefetch size. + setting of the prefetch size. A larger prefetch size results in + increased performance at the cost of higher memory usage. @@ -302,7 +303,8 @@ - + See the Errors and error + handling section for more information about this attribute. @@ -313,7 +315,8 @@ - + This is a read only attribute; it will return information about the + version of the database server to which PDO is connected. @@ -324,7 +327,8 @@ - + This is a read only attribute; it will return information about the + version of the client libraries that the PDO driver is using. @@ -335,7 +339,8 @@ - + This is a read only attribute; it will return some meta information about the + database server to which PDO is connected. @@ -369,7 +374,8 @@ - + Get or set the name to use for a cursor. Most useful when using + scrollable cursors and positioned updates. @@ -380,7 +386,11 @@ - + Selects the cursor type. PDO currently supports either + PDO_CURSOR_FWDONLY and + PDO_CURSOR_SCROLL. Stick with + PDO_CURSOR_FWDONLY unless you know that you need a + scrollable cursor. @@ -417,7 +427,7 @@ - Convert empty strings to SQL NULL values. + Convert empty strings to SQL NULL values on data fetches. @@ -429,6 +439,8 @@ Request a persistent connection, rather than creating a new connection. + See Connections and Connection + management for more information on this attribute. @@ -441,7 +453,8 @@ Prepend the containing catalog name to each column name returned in the result set. The catalog name and column name are separated by a decimal - (.) character. + (.) character. Support of this attribute is at the driver level; it may + not be supported by your driver. @@ -454,7 +467,8 @@ Prepend the containing table name to each column name returned in the result set. The table name and column name are separated by a decimal (.) - character. + character. Support of this attribute is at the driver level; it may not + be supported by your driver. @@ -467,6 +481,8 @@ Do not raise an error or exception if an error occurs. The developer is expected to explicitly check for errors. This is the default mode. + See Errors and error handling + for more information about this attribute. @@ -478,6 +494,8 @@ Issue a PHP E_WARNING message if an error occurs. + See Errors and error handling + for more information about this attribute. @@ -488,7 +506,9 @@ - Throw a PDOException if an error occurs. + Throw a PDOException if an error occurs. + See Errors and error handling + for more information about this attribute. @@ -601,9 +621,9 @@ - Create a PDOStatement object with a forward-only cursor. This may improve - the performance of your application but restricts your PDOStatement object - to fetching one row at a time from the result set in a forward direction. + Create a PDOStatement object with a forward-only cursor. This is the + default cursor choice, as it is the fastest and most common data access + pattern in PHP. @@ -627,7 +647,11 @@ Corresponds to SQLSTATE '0', meaning that the SQL statement was - successfully issued with no errors or warnings. + successfully issued with no errors or warnings. This constant is for + your convenience when checking PDO::errorCode or + PDOStatement::errorCode to determine if an error + occurred. You will usually know if this is the case by examining the + return code from the method that raised the error condition anyway. http://cvs.php.net/diff.p
[PHP-DOC] Re: PDO driver docs: volunteer needed for reformatting
PS: I can supply the original word/openoffice document to use as a guide for formatting the code parts. Please contact me if you'd like to take on this task. Many thanks again! --Wez. On 9/17/05, Wez Furlong <[EMAIL PROTECTED]> wrote: > Hello phpdoc, > > This was my commit message; I'm mentioning it here just in case a > suitable volunteer happened to skip over my commit. > > I'm looking for someone who has the time to reformat this document to > meet current phpdoc standards; I will then update it to match the > current PDO driver API. > > Thanks! > > --Wez. > > On 9/17/05, Wez Furlong <[EMAIL PROTECTED]> wrote: > > wez Sat Sep 17 21:13:08 2005 EDT > > > > Added files: > > /phpdoc/en/internals/pdoindex.xml > > Log: > > IBM has contributed an howto for creating PDO drivers. > > > > They supplied the text to me as a word doc, and I've converted that to > > Open Office and then used OOo2sDbk (http://www.chez.com/ebellot/ooo2sdbk/) > > to arrive at what you see here. > > > > This text is based on an older version of the driver API, and I will be > > updating this in the near future. > > > > I'd like to ask a phpdoc'er to volunteer to patch up the formatting to > > make > > it acceptable for inclusion in the manual before I do this; I'm really > > short > > on time right now, and I'm not up to speed with the latest phpdoc rules. > > > > Feel free to split this document out into multiple files as you see fit. > > > > Many thanks! >
[PHP-DOC] PDO driver docs: volunteer needed for reformatting
Hello phpdoc, This was my commit message; I'm mentioning it here just in case a suitable volunteer happened to skip over my commit. I'm looking for someone who has the time to reformat this document to meet current phpdoc standards; I will then update it to match the current PDO driver API. Thanks! --Wez. On 9/17/05, Wez Furlong <[EMAIL PROTECTED]> wrote: > wez Sat Sep 17 21:13:08 2005 EDT > > Added files: > /phpdoc/en/internals/pdoindex.xml > Log: > IBM has contributed an howto for creating PDO drivers. > > They supplied the text to me as a word doc, and I've converted that to > Open Office and then used OOo2sDbk (http://www.chez.com/ebellot/ooo2sdbk/) > to arrive at what you see here. > > This text is based on an older version of the driver API, and I will be > updating this in the near future. > > I'd like to ask a phpdoc'er to volunteer to patch up the formatting to make > it acceptable for inclusion in the manual before I do this; I'm really short > on time right now, and I'm not up to speed with the latest phpdoc rules. > > Feel free to split this document out into multiple files as you see fit. > > Many thanks!
[PHP-DOC] cvs: phpdoc /en/reference/win32service reference.xml
wez Sat Sep 17 19:30:39 2005 EDT Modified files: /phpdoc/en/reference/win32service reference.xml Log: typofix http://cvs.php.net/diff.php/phpdoc/en/reference/win32service/reference.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/win32service/reference.xml diff -u phpdoc/en/reference/win32service/reference.xml:1.1 phpdoc/en/reference/win32service/reference.xml:1.2 --- phpdoc/en/reference/win32service/reference.xml:1.1 Sat Sep 17 12:26:44 2005 +++ phpdoc/en/reference/win32service/reference.xml Sat Sep 17 19:30:38 2005 @@ -1,5 +1,5 @@ - + @@ -13,7 +13,7 @@ The win32service extension is a Windows specific extension that allows PHP to communicate with the Service Control Manager to start, stop, register -and unregister extensions, and even allows your PHP scripts to run as a +and unregister services, and even allows your PHP scripts to run as a service.
[PHP-DOC] cvs: phpdoc /en/reference/win32service .cvsignore constants.xml functions.xml reference.xml /en/reference/win32service/functions win32-create-service.xml win32-delete-service.xml win32-get-
wez Sat Sep 17 12:26:44 2005 EDT Added files: /phpdoc/en/reference/win32service .cvsignore constants.xml functions.xml reference.xml /phpdoc/en/reference/win32service/functions win32-create-service.xml win32-delete-service.xml win32-get-last-control-message.xml win32-query-service-status.xml win32-set-service-status.xml win32-start-service-ctrl-dispatcher.xml win32-start-service.xml win32-stop-service.xml Log: document win32 service extension http://cvs.php.net/co.php/phpdoc/en/reference/win32service/.cvsignore?r=1.1&p=1 Index: phpdoc/en/reference/win32service/.cvsignore +++ phpdoc/en/reference/win32service/.cvsignore functions.xml http://cvs.php.net/co.php/phpdoc/en/reference/win32service/constants.xml?r=1.1&p=1 Index: phpdoc/en/reference/win32service/constants.xml +++ phpdoc/en/reference/win32service/constants.xml &reftitle.constants; &extension.constants; WIN32_SERVICE_CONTROL_CONTINUE (integer) WIN32_SERVICE_CONTROL_INTERROGATE (integer) WIN32_SERVICE_CONTROL_PAUSE (integer) WIN32_SERVICE_CONTROL_STOP (integer) WIN32_SERVICE_CONTROL_HARDWAREPROFILECHANGE (integer) WIN32_SERVICE_CONTROL_POWEREVENT (integer) WIN32_SERVICE_CONTROL_SESSIONCHANGE (integer) WIN32_ERROR_CALL_NOT_IMPLEMENTED (integer) WIN32_NO_ERROR (integer) WIN32_SERVICE_RUNNING (integer) WIN32_SERVICE_STOPPED (integer) WIN32_SERVICE_STOP_PENDING (integer) WIN32_SERVICE_WIN32_OWN_PROCESS (integer) WIN32_SERVICE_INTERACTIVE_PROCESS (integer) WIN32_SERVICE_STOPPED (integer) WIN32_SERVICE_START_PENDING (integer) WIN32_SERVICE_STOP_PENDING (integer) WIN32_SERVICE_RUNNING (integer) WIN32_SERVICE_CONTINUE_PENDING (integer) WIN32_SERVICE_PAUSE_PENDING (integer) WIN32_SERVICE_PAUSED (integer) WIN32_SERVICE_ACCEPT_NETBINDCHANGE (integer) WIN32_SERVICE_ACCEPT_PARAMCHANGE (integer) WIN32_SERVICE_ACCEPT_PAUSE_CONTINUE (integer) WIN32_SERVICE_ACCEPT_SHUTDOWN (integer) WIN32_SERVICE_ACCEPT_STOP (integer) WIN32_SERVICE_ACCEPT_HARDWAREPROFILECHANGE (integer) WIN32_SERVICE_ACCEPT_POWEREVENT (integer) WIN32_SERVICE_ACCEPT_SESSIONCHANGE (integer) WIN32_SERVICE_FILE_SYSTEM_DRIVER (integer) WIN32_SERVICE_KERNEL_DRIVER (integer) WIN32_SERVICE_WIN32_SHARE_PROCESS (integer) WIN32_SERVICE_RUNS_IN_SYSTEM_PROCESS (integer) http://cvs.php.net/co.php/phpdoc/en/reference/win32service/functions.xml?r=1.1&p=1 Index: phpdoc/en/reference/win32service/functions.xml +++ phpdoc/en/reference/win32service/functions.xml &reference.win32service.functions.win32-create-service; &reference.win32service.functions.win32-delete-service; &reference.win32service.functions.win32-get-last-control-message; &reference.win32service.functions.win32-query-service-status; &reference.win32service.functions.win32-set-service-status; &reference.win32service.functions.win32-start-service-ctrl-dispatcher; &reference.win32service.functions.win32-start-service; &reference.win32service.functions.win32-stop-service; http://cvs.php.net/co.php/phpdoc/en/reference/win32service/reference.xml?r=1.1&p=1 Index: phpdoc/en/reference/win32service/reference.xml +++ phpdoc/en/reference/win32service/reference.xml
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml driverconstants.xml /en/reference/pdo_mysql constants.xml reference.xml /en/reference/pdo_pgsql reference.xml
wez Thu Sep 15 16:57:51 2005 EDT Added files: /phpdoc/en/reference/pdodriverconstants.xml /phpdoc/en/reference/pdo_mysql constants.xml Modified files: /phpdoc/en/reference/pdoconstants.xml /phpdoc/en/reference/pdo_mysql reference.xml /phpdoc/en/reference/pdo_pgsql reference.xml Log: more info on pdo http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.9&r2=1.10&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.9 phpdoc/en/reference/pdo/constants.xml:1.10 --- phpdoc/en/reference/pdo/constants.xml:1.9 Sun Sep 11 03:22:22 2005 +++ phpdoc/en/reference/pdo/constants.xml Thu Sep 15 16:57:50 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -394,6 +394,19 @@ Returns the name of the driver. + + using PDO_ATTR_DRIVER_NAME + + + + + http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_mysql/reference.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/reference/pdo_mysql/reference.xml diff -u phpdoc/en/reference/pdo_mysql/reference.xml:1.5 phpdoc/en/reference/pdo_mysql/reference.xml:1.6 --- phpdoc/en/reference/pdo_mysql/reference.xml:1.5 Sun Sep 11 02:17:08 2005 +++ phpdoc/en/reference/pdo_mysql/reference.xml Thu Sep 15 16:57:51 2005 @@ -1,5 +1,5 @@ - + @@ -11,12 +11,26 @@ &reftitle.intro; - &warn.experimental; PDO_MYSQL is a driver that implements the PHP Data Objects (PDO) interface to enable access from PHP to MySQL 3.x and 4.x databases. + + PDO_MYSQL will take advantage of native prepared statement support + present in MySQL 4.1 and higher. If you're using an older version of the + mysql client libraries, PDO will emulate them for you. + + + + Beware: MySQL tables do not support transactions by default. When + writing transactional database code, MySQL will pretend that a + transaction was initiated successfully, even when no transactional + support is present. In addition, any DDL queries issued will implicitly + commit any pending transactions. + + + &reference.pdo-mysql.constants; http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_pgsql/reference.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/reference/pdo_pgsql/reference.xml diff -u phpdoc/en/reference/pdo_pgsql/reference.xml:1.5 phpdoc/en/reference/pdo_pgsql/reference.xml:1.6 --- phpdoc/en/reference/pdo_pgsql/reference.xml:1.5 Sun Sep 11 02:17:08 2005 +++ phpdoc/en/reference/pdo_pgsql/reference.xml Thu Sep 15 16:57:51 2005 @@ -1,5 +1,5 @@ - + @@ -11,7 +11,6 @@ &reftitle.intro; - &warn.experimental; PDO_PGSQL is a driver that implements the PHP Data Objects (PDO) interface to enable access from PHP to PostgreSQL databases. http://cvs.php.net/co.php/phpdoc/en/reference/pdo/driverconstants.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo/driverconstants.xml +++ phpdoc/en/reference/pdo/driverconstants.xml The constants below are defined by this driver, and will only be available when the extension has been either compiled into PHP or dynamically loaded at runtime. In addition, these driver specific constants should only be used if you are using this driver. Using mysql specific attributes into the postgres driver may result in unexpected behaviour. You can use PDO::getAttribute to obtain the PDO_ATTR_DRIVER_NAME attribute to check the driver, if your code can run against multiple drivers. http://cvs.php.net/co.php/phpdoc/en/reference/pdo_mysql/constants.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_mysql/constants.xml +++ phpdoc/en/reference/pdo_mysql/constants.xml &reftitle.constants; &reference.pdo.driverconstants; PDO_MYSQL_ATTR_USE_BUFFERED_QUERY (integer) If this attribute is set to &true; on a PDOStatement, the MySQL driver will use the buffered versions of the MySQL API. If you're writing portable code, you should use PDOStatement::fetchAll instead. Forcing queries to be buffered in mysql
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sun Sep 11 23:44:39 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: fix interrupted sentence... http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.36&r2=1.37&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.36 phpdoc/en/reference/pdo/reference.xml:1.37 --- phpdoc/en/reference/pdo/reference.xml:1.36 Sun Sep 11 17:10:36 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 23:44:38 2005 @@ -1,5 +1,5 @@ - + @@ -26,7 +26,7 @@ functions to issue queries and fetch data. PDO does not provide a database abstraction; it doesn't rewrite SQL or emulate missing features. You - should use a full-blown abstraction layer for PDO. + should use a full-blown abstraction layer if you need that facility. PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0;
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sun Sep 11 17:10:37 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: Add some content. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.35&r2=1.36&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.35 phpdoc/en/reference/pdo/reference.xml:1.36 --- phpdoc/en/reference/pdo/reference.xml:1.35 Sun Sep 11 03:22:22 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 17:10:36 2005 @@ -1,5 +1,5 @@ - + @@ -21,6 +21,14 @@ PDO driver to access a database server. + PDO provides a data-access abstraction layer, which + means that, regardless of which database you're using, you use the same + functions to issue queries and fetch data. PDO does + not provide a database + abstraction; it doesn't rewrite SQL or emulate missing features. You + should use a full-blown abstraction layer for PDO. + + PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0; PDO requires the new OO features in the core of PHP 5, and so will not run with earlier versions of PHP. @@ -216,6 +224,522 @@ + +Connections and Connection management + + Connections are established by creating instances of the PDO base class. + It doesn't matter which driver you want to use; you always use the PDO + class name. The constructor accepts parameters for specifying the + database source (known as the DSN) and optionally for the username and + password (if any). + + + Connecting to mysql + + + + + + + If there are any connection errors, a PDOException + object will be thrown. You may catch the exception if you want to handle + the error condition, or you may opt to leave it for an application + global exception handler that you set up via + set_exception_handler. + + + Handling connection errors + + + + + + + Upon successful connection to the database, an instance of the PDO class + is returned to your script. The connection remains active for the + lifetime of that PDO object. To close the connection, you need to + destroy the object by ensuring that all remaining references to it are + deleted--you do this by assigning &null; to the variable that holds the + object. If you don't do this explicitly, PHP will automatically close + the connection when your script ends. + + + Closing a connection + + + + + + +Many web applications will benefit from making persistent connections to +database servers. Persistent connections are not closed at the end of the +script, but are cached and re-used when another script requests a +connection using the same credentials. The persistent connection cache +allows you to avoid the overhead of establishing a new connection every +time a script needs to talk to a database, resulting in a faster web +application. + + +Persistent connections + + + + + + + + If you're using the PDO ODBC driver and your ODBC libraries support ODBC + Connection Pooling (unixODBC and Windows are two that do; there may be + more), then it's recommended that you don't use persistent PDO + connections, and instead leave the connection caching to the ODBC + Connection Pooling layer. The ODBC Connection Pool is shared with other + modules in the process; if PDO is told to cache the connection, then + that connection would never be returned to the ODBC connection pool, + resulting in additional connections being created to service those other + modules. + + + + + +Transactions and auto-commit + + Now that you're connected via PDO, you should to understand how PDO + manages transactions before you start issuing queries. If you've never + encountered transactions before, they offer 4 major features: Atomicity, + Consistency, Isolation and Durability (ACID). In layman's terms, any work + carried out in a transaction, even if it is carried out in stages, is + guaranteed to be applied to the database safely, and without interference + from other connections, when it is committed. Transactional work can also + be automatically undone at your request (provided you haven't already + committed it), which makes error handling in your scripts easier. + + + Transactions are typically implemented by "saving-up" your batch of + changes to be applied all at once; this has the nice side effect of + drastically improving the efficiency of those updates. In other words, + transactions can make your scripts faster and potentially more robust + (you still need to use them correctly to reap that benefit). + + + Unfortunately, not
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml reference.xml
wez Sun Sep 11 03:22:23 2005 EDT Modified files: /phpdoc/en/reference/pdoconstants.xml reference.xml Log: The extension is no longer experimental; what we have is not going to change between now and the first stable release. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.8 phpdoc/en/reference/pdo/constants.xml:1.9 --- phpdoc/en/reference/pdo/constants.xml:1.8 Mon Jul 11 00:38:54 2005 +++ phpdoc/en/reference/pdo/constants.xml Sun Sep 11 03:22:22 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -7,6 +7,18 @@ +PDO_PARAM_BOOL + (integer) + + + + Represents a boolean data type. + + + + + + PDO_PARAM_NULL (integer) @@ -596,116 +608,6 @@ -PDO_ERR_CANT_MAP - (integer) - - - - - - - - - -PDO_ERR_SYNTAX - (integer) - - - - - - - - - -PDO_ERR_CONSTRAINT - (integer) - - - - - - - - - -PDO_ERR_NOT_FOUND - (integer) - - - - - - - - - -PDO_ERR_ALREADY_EXISTS - (integer) - - - - - - - - - -PDO_ERR_NOT_IMPLEMENTED - (integer) - - - - - - - - - -PDO_ERR_MISMATCH - (integer) - - - - - - - - - -PDO_ERR_TRUNCATED - (integer) - - - - - - - - - -PDO_ERR_DISCONNECTED - (integer) - - - - - - - - - -PDO_ERR_NO_PERM - (integer) - - - - - - - - - PDO_ERR_NONE (string) http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.34&r2=1.35&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.34 phpdoc/en/reference/pdo/reference.xml:1.35 --- phpdoc/en/reference/pdo/reference.xml:1.34 Sun Sep 11 02:17:05 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 03:22:22 2005 @@ -1,5 +1,5 @@ - + @@ -12,7 +12,6 @@ &reftitle.intro; - &warn.experimental; The PHP Data Objects (PDO) extension defines a lightweight, consistent interface for accessing databases in PHP. Each database driver that implements the PDO interface can expose database-specific @@ -122,6 +121,10 @@ ]]> + + For more information about building PECL packages, consult the + PECL installation section of the manual. +
[PHP-DOC] cvs: phpdoc /en/install pecl.xml
wez Sun Sep 11 03:18:59 2005 EDT Modified files: /phpdoc/en/install pecl.xml Log: adjust pecl installation notes http://cvs.php.net/diff.php/phpdoc/en/install/pecl.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/install/pecl.xml diff -u phpdoc/en/install/pecl.xml:1.8 phpdoc/en/install/pecl.xml:1.9 --- phpdoc/en/install/pecl.xml:1.8 Tue Jun 7 18:41:44 2005 +++ phpdoc/en/install/pecl.xml Sun Sep 11 03:18:57 2005 @@ -1,5 +1,5 @@ - + Installation of PECL extensions @@ -7,27 +7,27 @@ Introduction to PECL Installations - PHP extensions may be installed in a variety of ways. - PECL is a repository of PHP extensions - living within the PEAR structure, and - the following demonstrates how to install these extensions. + PECL is a repository of PHP extensions that + are made available to you via the PEAR + packaging system. This section of the manual is intended to demonstrate + how to obtain and install PECL extensions. These instructions assume /your/phpsrcdir/ is the path - to the PHP source, and extname is the name of the + to the PHP source distribution, and that extname is the name of the PECL extension. Adjust accordingly. These instructions also assume a familiarity with the pear command. - Shared extensions may be installed by including them inside of &php.ini; - using the extension PHP directive. See - also the extensions_dir - directive, and dl. The installation methods described - below do not automatically configure PHP to include these extensions, this - step must be done manually. + To be useful, a shared extension must be built, installed, and loaded. The + methods described below provide you with various instructions on how to + build and install the extensions, but they do not automatically load them. + Extensions can be loaded by adding an extension directive. To this &php.ini; + file, or through the use of the dl function. - When building PHP modules, it's important to have the appropriate versions + When building PHP modules, it's important to have known-good versions of the required tools (autoconf, automake, libtool, etc.) See the Anonymous CVS Instructions for details on the required tools, and required versions. @@ -45,9 +45,10 @@ &url.pecl; - Listed here is information like the ChangeLog, release information, - requirements, revisions, etc. Although not every PECL extension has a - webpage, most do. + The PECL web site contains information about the different extensions + that are offered by the PHP Development Team. The information available + here includes: ChangeLog, release notes, requirements and other similar + details. @@ -55,8 +56,10 @@ pear download extname - The pear command may also be used - to download source files. Specific revisions may also be specified. + PECL extensions that have releases listed on the PECL web site are + available for download and installation using the pear command. + Specific revisions may also be specified. @@ -64,10 +67,10 @@ CVS - All PECL files reside in CVS. A web-based view may + Most PECL extensions also reside in CVS. A web-based view may be seen at &url.php.cvs;pecl/. - To download straight from CVS, consider the following - where phpfi is the password for user + To download straight from CVS, the following + sequence of commands may be used. Note that phpfi is the password for user cvsread: @@ -96,10 +99,10 @@ PECL for Windows users - Like with any other PHP extension DLL, to install move - the PECL extension DLLs into the - extension_dir folder and include them within &php.ini;. For - example: + As with any other PHP extension DLL, installation is as + simple as copying the PECL extension DLLs into the + extension_dir folder and loading them from &php.ini;. For + example, add the following line to your &php.ini;: @@ -123,67 +126,75 @@ - That will download the source for extname, and - compile it on the system. This results in an - extname.so file that may then be included in &php.ini; + This will download the source for extname, + compile, and install extname.so into your extension_dir. + extname.so may then be loaded via &php.ini; - In case the systems preferred_state is set higher than - an available extname version, like it's set to stable - and the extension is still in beta, either alter the - preferred_state via pear config-set - or specify a specific version of the PECL extension. For example: + By default, the pear command will not install + packages that are marked with the alpha or + beta state. If no stable packages + are available, you may install a beta package usi
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-beginTransaction.xml PDO-commit.xml PDO-construct.xml PDO-errorCode.xml PDO-errorInfo.xml PDO-exec.xml PDO-getAttribute.xml PDO-lastInsertId.xml P
wez Sun Sep 11 02:22:29 2005 EDT Modified files: /phpdoc/en/reference/pdo/functions PDO-beginTransaction.xml PDO-commit.xml PDO-construct.xml PDO-errorCode.xml PDO-errorInfo.xml PDO-exec.xml PDO-getAttribute.xml PDO-lastInsertId.xml PDO-prepare.xml PDO-query.xml PDO-quote.xml PDO-rollBack.xml PDO-setAttribute.xml PDOStatement-bindColumn.xml PDOStatement-bindParam.xml PDOStatement-bindValue.xml PDOStatement-closeCursor.xml PDOStatement-columnCount.xml PDOStatement-errorCode.xml PDOStatement-errorInfo.xml PDOStatement-execute.xml PDOStatement-fetch.xml PDOStatement-fetchAll.xml PDOStatement-fetchColumn.xml PDOStatement-nextRowset.xml PDOStatement-rowCount.xml PDOStatement-setFetchMode.xml pdo-drivers.xml Log: All these methods are stable. Note: getColumnMeta is not stable; the warning was intentionally left there. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml diff -u phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.4 phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.5 --- phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.4 Wed Aug 24 07:07:44 2005 +++ phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml Sun Sep 11 02:22:26 2005 @@ -1,5 +1,5 @@ - + @@ -15,7 +15,6 @@ boolPDO::beginTransaction -&warn.experimental.func; Turns off autocommit mode. While autocommit mode is turned off, changes made to the database via the PDO object instance are not committed until http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-commit.xml?r1=1.2&r2=1.3&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-commit.xml diff -u phpdoc/en/reference/pdo/functions/PDO-commit.xml:1.2 phpdoc/en/reference/pdo/functions/PDO-commit.xml:1.3 --- phpdoc/en/reference/pdo/functions/PDO-commit.xml:1.2Sat Feb 5 13:52:58 2005 +++ phpdoc/en/reference/pdo/functions/PDO-commit.xmlSun Sep 11 02:22:26 2005 @@ -1,5 +1,5 @@ - + @@ -15,7 +15,6 @@ boolPDO::commit -&warn.experimental.func; Commits a transaction, returning the database connection to autocommit mode until the next call to PDO::beginTransaction http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-construct.xml?r1=1.14&r2=1.15&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-construct.xml diff -u phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.14 phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.15 --- phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.14Wed Aug 24 07:13:06 2005 +++ phpdoc/en/reference/pdo/functions/PDO-construct.xml Sun Sep 11 02:22:26 2005 @@ -1,5 +1,5 @@ - + PDO::__construct @@ -16,7 +16,6 @@ stringpassword arraydriver_options -&warn.experimental.func; Creates a PDO instance to represent a connection to the requested database. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-errorCode.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-errorCode.xml diff -u phpdoc/en/reference/pdo/functions/PDO-errorCode.xml:1.5 phpdoc/en/reference/pdo/functions/PDO-errorCode.xml:1.6 --- phpdoc/en/reference/pdo/functions/PDO-errorCode.xml:1.5 Mon Jul 11 00:38:55 2005 +++ phpdoc/en/reference/pdo/functions/PDO-errorCode.xml Sun Sep 11 02:22:26 2005 @@ -1,5 +1,5 @@ - + @@ -15,7 +15,6 @@ - &warn.experimental.func; http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml?r1=1.6&r2=1.7&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml diff -u phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml:1.6 phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml:1.7 --- phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml:1.6 Mon Jul 11 00:38:55 2005 +++ phpdoc/en/reference/pdo/functions/PDO-errorInfo.xml Sun Sep 11 02:22:2
[PHP-DOC] cvs: phpdoc /en/reference/pdo ini.xml reference.xml /en/reference/pdo_dblib reference.xml /en/reference/pdo_firebird reference.xml /en/reference/pdo_mysql reference.xml /en/reference/pdo
wez Sun Sep 11 02:17:10 2005 EDT Added files: /phpdoc/en/reference/pdo_odbc ini.xml Modified files: /phpdoc/en/reference/pdoini.xml reference.xml /phpdoc/en/reference/pdo_dblib reference.xml /phpdoc/en/reference/pdo_firebird reference.xml /phpdoc/en/reference/pdo_mysql reference.xml /phpdoc/en/reference/pdo_ocireference.xml /phpdoc/en/reference/pdo_odbc reference.xml /phpdoc/en/reference/pdo_pgsql reference.xml /phpdoc/en/reference/pdo_sqlite reference.xml Log: Juggle and update http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/ini.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/pdo/ini.xml diff -u phpdoc/en/reference/pdo/ini.xml:1.1 phpdoc/en/reference/pdo/ini.xml:1.2 --- phpdoc/en/reference/pdo/ini.xml:1.1 Wed Aug 10 04:36:30 2005 +++ phpdoc/en/reference/pdo/ini.xml Sun Sep 11 02:17:05 2005 @@ -1,5 +1,5 @@ - + &reftitle.runtime; &extension.runtime; @@ -22,12 +22,6 @@ &php.ini; only - - pdo_odbc.connection_pooling - "strict" - PHP_INI_ALL - - @@ -51,19 +45,6 @@ - - -pdo_odbc.connection_pooling -string - - - - Whether to pool ODBC connections. Can be one of "strict", "relaxed" or - "off" (equals to ""). - - - - http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.33&r2=1.34&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.33 phpdoc/en/reference/pdo/reference.xml:1.34 --- phpdoc/en/reference/pdo/reference.xml:1.33 Fri Sep 9 11:13:53 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 02:17:05 2005 @@ -1,5 +1,5 @@ - + @@ -248,12 +248,6 @@ - exec - - issues an SQL statement and returns the number of affected rows - - - - errorCode - retrieves an error code, if any, from the database @@ -267,6 +261,12 @@ + exec + - issues an SQL statement and returns the number of affected rows + + + + getAttribute - retrieves a database connection attribute @@ -333,6 +333,12 @@ + bindValue + - binds a value to a parameter in the prepared statement + + + + closeCursor - closes the cursor, allowing the statement to be executed again http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_dblib/reference.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/reference/pdo_dblib/reference.xml diff -u phpdoc/en/reference/pdo_dblib/reference.xml:1.4 phpdoc/en/reference/pdo_dblib/reference.xml:1.5 --- phpdoc/en/reference/pdo_dblib/reference.xml:1.4 Sun Sep 4 15:39:24 2005 +++ phpdoc/en/reference/pdo_dblib/reference.xml Sun Sep 11 02:17:07 2005 @@ -1,5 +1,5 @@ - + @@ -12,15 +12,15 @@ &reftitle.intro; &warn.experimental; - PDO_DBLIB is a driver that implements the PHP Data Objects (PDO) interface - to enable access from PHP to Microsoft SQL Server and Sybase databases - through the FreeTDS libary. + PDO_DBLIB is a driver that implements the PHP + Data Objects (PDO) interface to enable access from PHP to + Microsoft SQL Server and Sybase databases through the FreeTDS libary. On Windows, you should use the PDO_ODBC - driver to connect to Microsoft SQL Server and Sybase databases, as PDO_ODBC - is built directly against the Microsoft Windows ODBC Driver Manager - libraries. + driver to connect to Microsoft SQL Server and Sybase databases, as the + native Windows DB-LIB is ancient, thread un-safe and no longer supported + by Microsoft. @@ -41,8 +41,10 @@ The DSN prefix is sybase: if PDO_DBLIB was -linked against the FreeTDS libraries, or mssql: -if PDO_DBLIB was linked against the Microsoft SQL Server libraries. +linked against the FreeTDS libraries, mssql: +if PDO_DBLIB was linked against the Microsoft SQL Server libraries, +or dblib: if linked against any other variety +of DB-lib. @@ -76,6 +78,7 @@ http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_firebird/reference.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/reference/pdo_firebird/reference.xml diff -u phpdoc/en/reference/pdo_firebird/reference.xml:1.4 phpdoc/en/reference/pdo_firebird/reference.xml:1.5 --- phpdoc/en/reference/pdo_firebird/reference.xml:1.4 Sun Sep 4 15:39:24 2005 +++ phpdoc/en/reference/pdo_firebird/reference.xml Sun Sep 11 02:17:07 2005 @@ -1,5 +1,5 @@ - + @@ -12,8 +12,8 @@ &reftitle.intro; &warn.experimental; - PDO_FIREBIRD i
[PHP-DOC] cvs: phpdoc /en/reference/pdo_odbc reference.xml
wez Sat Sep 10 20:52:08 2005 EDT Modified files: /phpdoc/en/reference/pdo_odbc reference.xml Log: MS Access sample http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_odbc/reference.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/reference/pdo_odbc/reference.xml diff -u phpdoc/en/reference/pdo_odbc/reference.xml:1.4 phpdoc/en/reference/pdo_odbc/reference.xml:1.5 --- phpdoc/en/reference/pdo_odbc/reference.xml:1.4 Sun Sep 4 15:39:24 2005 +++ phpdoc/en/reference/pdo_odbc/reference.xml Sat Sep 10 20:52:05 2005 @@ -1,5 +1,5 @@ - + @@ -106,7 +106,19 @@ - + + PDO_ODBC DSN example (Microsoft Access uncataloged connection) + + The following example shows a PDO_ODBC DSN for connecting to + a Microsoft Access database stored at C:\db.mdb using the full + ODBC DSN syntax: + + + + +
[PHP-DOC] cvs: phpdoc /en/reference/pdo_sqlite reference.xml /en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml
wez Sat Sep 10 12:45:53 2005 EDT Modified files: /phpdoc/en/reference/pdo_sqlite reference.xml /phpdoc/en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml Log: these aren't present for the sqlite2 driver. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/reference.xml?r1=1.6&r2=1.7&ty=u Index: phpdoc/en/reference/pdo_sqlite/reference.xml diff -u phpdoc/en/reference/pdo_sqlite/reference.xml:1.6 phpdoc/en/reference/pdo_sqlite/reference.xml:1.7 --- phpdoc/en/reference/pdo_sqlite/reference.xml:1.6Sat Sep 10 11:44:37 2005 +++ phpdoc/en/reference/pdo_sqlite/reference.xmlSat Sep 10 12:45:51 2005 @@ -1,5 +1,5 @@ - + @@ -18,8 +18,12 @@ In PHP 5.1, the SQLite extension also provides a driver for SQLite 2 databases; while it is not technically a - part of the PDO_SQLITE driver, it behaves very similarly, so it is - documented alongside it. + part of the PDO_SQLITE driver, it behaves similarly, so it is + documented alongside it. The SQLite 2 driver for PDO is provided + primarily to make it easier to import legacy sqlite 2 database files into + an application that uses the faster, more efficient sqlite 3 driver. As + a result, the SQLite 2 driver is not as feature-rich as the SQLite 3 + driver. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml diff -u phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.3 phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.4 --- phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.3 Fri Sep 9 12:50:02 2005 +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml Sat Sep 10 12:45:52 2005 @@ -1,5 +1,5 @@ - + PDO::sqliteCreateAggregate @@ -163,6 +163,13 @@ SQL functions. + + +This method is not available with the SQLite2 driver. +Use the old style sqlite API for that instead. + + + @@ -171,6 +178,8 @@ PDO::sqliteCreateFunction +sqlite_create_function +sqlite_create_aggregate http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml diff -u phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.3 phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.4 --- phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.3 Fri Sep 9 12:50:02 2005 +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml Sat Sep 10 12:45:53 2005 @@ -1,5 +1,5 @@ - + PDO::sqliteCreateFunction @@ -132,13 +132,21 @@ SQL functions. + + +This method is not available with the SQLite2 driver. +Use the old style sqlite API for that instead. + + &reftitle.seealso; - PDO::sqliteCreateAggregate +PDO::sqliteCreateAggregate +sqlite_create_function +sqlite_create_aggregate
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDOStatement-bindParam.xml PDOStatement-bindValue.xml
wez Sat Sep 10 12:39:22 2005 EDT Added files: /phpdoc/en/reference/pdo/functions PDOStatement-bindValue.xml Modified files: /phpdoc/en/reference/pdo/functions PDOStatement-bindParam.xml Log: Document new bindValue() method. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xml diff -u phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xml:1.8 phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xml:1.9 --- phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xml:1.8Mon Jul 11 08:31:57 2005 +++ phpdoc/en/reference/pdo/functions/PDOStatement-bindParam.xmlSat Sep 10 12:39:21 2005 @@ -1,5 +1,5 @@ - + @@ -20,8 +20,11 @@ &warn.experimental.func; - Binds a parameter to a corresponding named or question mark placeholder - in the SQL statement that was use to prepare the statement. + Binds a PHP variable to a corresponding named or question mark placeholder + in the SQL statement that was use to prepare the statement. Unlike + PDOStatement::bindValue, the variable is bound as a + reference and will only be evaluated at the time that + PDOStatement::execute is called. Most parameters are input parameters, that is, parameters that are used @@ -173,6 +176,7 @@ PDO::prepare PDOStatement::execute + PDOStatement::bindValue http://cvs.php.net/co.php/phpdoc/en/reference/pdo/functions/PDOStatement-bindValue.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo/functions/PDOStatement-bindValue.xml +++ phpdoc/en/reference/pdo/functions/PDOStatement-bindValue.xml PDOStatement::bindValue Binds a value to a parameter &reftitle.description; boolPDOStatement::bindValue mixedparameter mixedvalue intdata_type &warn.experimental.func; Binds a value to a corresponding named or question mark placeholder in the SQL statement that was use to prepare the statement. &reftitle.parameters; parameter Parameter identifier. For a prepared statement using named placeholders, this will be a parameter name of the form :name. For a prepared statement using question mark placeholders, this will be the 1-indexed position of the parameter. value The value to bind to the parameter. data_type Explicit data type for the parameter using the PDO_PARAM_* constants. &reftitle.examples; Execute a prepared statement with named placeholders Execute a prepared statement with question mark placeholders &reftitle.seealso; PDO::prepare PDOStatement::execute PDOStatement::bindParam
[PHP-DOC] cvs: phpdoc / Makefile.in
wez Sat Sep 10 12:20:30 2005 EDT Modified files: /phpdoc Makefile.in Log: use portable test -f instead of test -e http://cvs.php.net/diff.php/phpdoc/Makefile.in?r1=1.169&r2=1.170&ty=u Index: phpdoc/Makefile.in diff -u phpdoc/Makefile.in:1.169 phpdoc/Makefile.in:1.170 --- phpdoc/Makefile.in:1.169Sun Aug 21 12:27:02 2005 +++ phpdoc/Makefile.in Sat Sep 10 12:20:28 2005 @@ -16,7 +16,7 @@ # # -# $Id: Makefile.in,v 1.169 2005/08/21 16:27:02 goba Exp $ +# $Id: Makefile.in,v 1.170 2005/09/10 16:20:28 wez Exp $ # all: html @@ -165,7 +165,7 @@ quickref: quickref.txt quickref.txt: FORCE - @if test ! -e funcindex.xml; then touch funcindex.xml; fi + @if test ! -f funcindex.xml; then touch funcindex.xml; fi $(XSLTPROC) -o quickref.txt $(QUICKREF_XSL_SHEET) manual.xml kdevelop_toc: php.toc @@ -307,22 +307,22 @@ # test all possible errors test: manual.xml - @if test ! -e funcindex.xml; then touch funcindex.xml; fi - @if test ! -e entities/missing-entities.ent; then touch entities/missing-entities.ent; fi - @if test ! -e entities/missing-ids.xml; then touch entities/missing-ids.xml; fi + @if test ! -f funcindex.xml; then touch funcindex.xml; fi + @if test ! -f entities/missing-entities.ent; then touch entities/missing-entities.ent; fi + @if test ! -f entities/missing-ids.xml; then touch entities/missing-ids.xml; fi $(NSGMLS) -i lang-$(LANG) -s $(XMLDCL) manual.xml # ignore missing IDs and check if the manual can be generated anyway test_man_gen: manual.xml - @if test ! -e funcindex.xml; then touch funcindex.xml; fi - @if test ! -e entities/missing-entities.ent; then touch entities/missing-entities.ent; fi - @if test ! -e entities/missing-ids.xml; then touch entities/missing-ids.xml; fi + @if test ! -f funcindex.xml; then touch funcindex.xml; fi + @if test ! -f entities/missing-entities.ent; then touch entities/missing-entities.ent; fi + @if test ! -f entities/missing-ids.xml; then touch entities/missing-ids.xml; fi $(NSGMLS) -wno-idref -i lang-$(LANG) -s $(XMLDCL) manual.xml test_xml: manual.xml - @if test ! -e funcindex.xml; then touch funcindex.xml; fi - @if test ! -e entities/missing-entities.ent; then touch entities/missing-entities.ent; fi - @if test ! -e entities/missing-ids.xml; then touch entities/missing-ids.xml; fi + @if test ! -f funcindex.xml; then touch funcindex.xml; fi + @if test ! -f entities/missing-entities.ent; then touch entities/missing-entities.ent; fi + @if test ! -f entities/missing-ids.xml; then touch entities/missing-ids.xml; fi $(XMLLINT) --noent --noout --valid manual.xml test_howto:
[PHP-DOC] cvs: phpdoc /en/reference/pdo_sqlite reference.xml /en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml
wez Fri Sep 9 00:10:15 2005 EDT Modified files: /phpdoc/en/reference/pdo_sqlite reference.xml /phpdoc/en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml Log: tweak. livedocs won't let me view the those two function pages, so I hope they are ok. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/reference.xml?r1=1.4&r2=1.5&ty=u Index: phpdoc/en/reference/pdo_sqlite/reference.xml diff -u phpdoc/en/reference/pdo_sqlite/reference.xml:1.4 phpdoc/en/reference/pdo_sqlite/reference.xml:1.5 --- phpdoc/en/reference/pdo_sqlite/reference.xml:1.4Sun Sep 4 15:39:25 2005 +++ phpdoc/en/reference/pdo_sqlite/reference.xmlFri Sep 9 00:10:10 2005 @@ -1,5 +1,5 @@ - + @@ -13,7 +13,13 @@ &warn.experimental; PDO_SQLITE is a driver that implements the PHP Data Objects (PDO) interface - to enable access to SQLite 2 and SQLite 3 databases. + to enable access to SQLite 3 databases. + + + In PHP 5.1, the SQLite extension also + provides a driver for SQLite 2 databases; while it is not technically a + part of the PDO_SQLITE driver, it behaves very similarly, so it is + documented alongside it. @@ -55,12 +61,18 @@ DSN prefix (SQLite 2) - While the default and recommended SQLite version in PDO_SQLITE is - version 3, the driver also supports accessing and creating SQLite 2 - databases. This enables you to access databases you may have created + The SQLite extension in + PHP 5.1 provides a PDO driver that supports accessing and creating SQLite 2 + databases. This enables you to access databases you may have created with the SQLite extension in previous versions of PHP. + + + The sqlite2 driver is only available in PHP 5.1 if you have enabled + both PDO and ext/sqlite. It is not currently available via PECL. + + The DSN prefix for connecting to SQLite 2 databases is sqlite2:. @@ -95,9 +107,9 @@ SQLite databases: http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml diff -u phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.1 phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.2 --- phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml:1.1 Thu Sep 8 23:25:36 2005 +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml Fri Sep 9 00:10:14 2005 @@ -1,5 +1,5 @@ - + PDO::sqliteCreateAggregate @@ -174,6 +174,7 @@ PDO::sqliteCreateFunction + http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml diff -u phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.1 phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.2 --- phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml:1.1 Thu Sep 8 23:25:37 2005 +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml Fri Sep 9 00:10:15 2005 @@ -1,5 +1,5 @@ - + PDO::sqliteCreateFunction @@ -142,6 +142,7 @@ PDO::sqliteCreateAggregate +
[PHP-DOC] cvs: phpdoc /en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml
wez Thu Sep 8 23:25:38 2005 EDT Added files: /phpdoc/en/reference/pdo_sqlite/functions PDO-sqliteCreateAggregate.xml PDO-sqliteCreateFunction.xml Log: Document sqlite specific functions for PDO. http://cvs.php.net/co.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateAggregate.xml PDO::sqliteCreateAggregate Registers an aggregating User Defined Function for use in SQL statements &reftitle.description; boolPDO::sqliteCreateAggregate stringfunction_name callbackstep_func callbackfinalize_func intnum_args &warn.experimental.func; PDO::sqliteCreateAggregate is similar to PDO::sqliteCreateFunction except that it registers functions that can be used to calculate a result aggregated across all the rows of a query. The key difference between this function and PDO::sqliteCreateFunction is that two functions are required to manage the aggregate; step_func is called for each row of the result set. Your PHP function should accumulate the result and store it into the aggregation context. Once all the rows have been processed, finalize_func will be called and it should then take the data from the aggregation context and return the result. Callback functions should return a type understood by SQLite (i.e. scalar type). &reftitle.parameters; function_name The name of the function used in SQL statements. step_func Callback function called for each row of the result set. finalize_func Callback function to aggregate the "stepped" data from each row. num_args Hint to the SQLite parser if the callback function accepts a predetermined number of arguments. &reftitle.examples; max_length aggregation function example In this example, we are creating an aggregating function that will calculate the length of the longest string in one of the columns of the table. For each row, the max_len_step function is called and passed a context parameter. The context parameter is just like any other PHP variable and be set to hold an array or even an object value. In this example, we are simply using it to hold the maximum length we have seen so far; if the string has a length longer than the current maximum, we update the context to hold this new maximum length. After all of the rows have been processed, SQLite calls the max_len_finalize function to determine the aggregate result. Here, we could perform some kind of calculation based on the data found in the context. In our simple example though, we have been calculating the result as the query progressed, so we simply need to return the context value. It is NOT recommended for you to store a copy of the values in the context and then process them at the end, as you would cause SQLite to use a lot of memory to process the query - just think of how much memory you would need if a million rows were stored in memory, each containing a string 32 bytes in length. You can use PDO::sqliteCreateFunction and PDO::sqliteCreateAggregate to override SQLite native SQL functions. &reftitle.seealso; PDO::sqliteCreateFunction http://cvs.php.net/co.php/phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml?r=1.1&p=1 Index: phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml +++ phpdoc/en/reference/pdo_sqlite/functions/PDO-sqliteCreateFunction.xml PDO::sqliteCreateFunction Registers a User Defined Function for use in SQL statements &reftitle.description; boolPDO::sqliteCreateFunction stringfunction_name callbackcallback intnum_args &warn.experimental.func; PDO::sqliteCreateFunction allows you to register a PHP function with SQLite as an UDF (User Defined Function), so that it can be called from within your SQL statements. The UDF can be used in any SQL statement that can call functions, such as SELECT and UPDATE statements and also in triggers. &reftitle.parameters; function_name The name of the function used in SQL statements. callback Callback function to handle the defined SQL function. Callback functions
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Thu Sep 8 23:00:48 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: revise install instructions http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.30&r2=1.31&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.30 phpdoc/en/reference/pdo/reference.xml:1.31 --- phpdoc/en/reference/pdo/reference.xml:1.30 Sun Sep 4 15:39:23 2005 +++ phpdoc/en/reference/pdo/reference.xml Thu Sep 8 23:00:46 2005 @@ -1,5 +1,5 @@ - + @@ -21,59 +21,101 @@ itself; you must use a database-specific PDO driver to access a database server. + + PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0; + PDO requires the new OO features in the core of PHP 5, and so will not + run with earlier versions of PHP. + &reftitle.install; - - - - Windows + + - Follow the same steps to install and enable the PDO drivers of your - choice. + Having PDO as a shared module will allow you to run pear + upgrade pdo as new versions of PDO are published, without + forcing you to rebuild the whole of PHP. Note that if you do this, you + also need to upgrade your database specific PDO drivers at the same + time. + + + PHP 5.0 and up on Unix systems + + PDO is available as a PECL extension from + &url.pecl.package;pdo. + Installation can be performed via the pear tool; this + is enabled by default when you configure PHP. You should ensure that + PHP was configured --with-zlib in order for + pear to be able to handle the compressed package + files. + + + Run the following command to download, build, and install the + latest stable version of PDO: + + + + + + If PDO is still in beta (and at the time of writing, it is), you will + need to tell the pear tool that it's ok to fetch the beta package. + Instead of running the command above, run the following: + + + + + + The pear command automatically installs the + PDO module into your PHP extensions directory. To enable the + PDO extension on Linux or Unix operating systems, you must add + the following line to &php.ini;: + + + + + + + Windows users running PHP 5.1 and up - Windows users can download the extension DLL php_pdo.dll - as part of the PECL collection binaries from - &url.php.downloads; or a more - recent version from a PHP 5 PECL - Snapshot. - - - - - To enable the PDO extension on Windows operating systems, you must - add the following line to &php.ini;: + PDO and all the major drivers ship with PHP as shared extensions, and + simply need to be activated by editing the &php.ini; file: - - - - - - Determine your PHP bin directory. If your - PHP 5 CLI binary lives at /usr/local/php5/bin/php - then the bin dir is /usr/local/php5/bin. - - - - - Set your path so that your PHP bin directory - is at the front: - - - - - - - - Manually build and install the PDO extension: - - - - - - &reference.pdo.ini;
[PHP-DOC] cvs: livedocs / README
wez Thu Sep 8 22:17:16 2005 EDT Modified files: /livedocs README Log: solaris /bin/sh doesn't grok "exec >file"; run with ksh instead http://cvs.php.net/diff.php/livedocs/README?r1=1.15&r2=1.16&ty=u Index: livedocs/README diff -u livedocs/README:1.15 livedocs/README:1.16 --- livedocs/README:1.15Wed Feb 9 13:15:53 2005 +++ livedocs/README Thu Sep 8 22:17:14 2005 @@ -1,6 +1,6 @@ README == -$Id: README,v 1.15 2005/02/09 18:15:53 edink Exp $ +$Id: README,v 1.16 2005/09/09 02:17:14 wez Exp $ vim:et:tw=78 INTRODUCTION @@ -83,6 +83,8 @@ ./build.sh +On Solaris, you need to run "ksh ./build.sh" instead. + This creates phpdoc-idx.$LANG.sqlite and livedoc-cache-idx.$LANG.sqlite. It will also configure phpdoc (autoconf & ./configure).
[PHP-DOC] cvs: phpdoc /en/reference/oci8/functions oci-free-descriptor.xml ocigetbufferinglob.xml ocisetbufferinglob.xml
wez Tue Sep 6 16:09:51 2005 EDT Removed files: /phpdoc/en/reference/oci8/functions oci-free-descriptor.xml ocigetbufferinglob.xml ocisetbufferinglob.xml Log: more files renamed
[PHP-DOC] cvs: phpdoc /en/reference/oci8/functions oci-lob-append.xml oci-lob-close.xml oci-lob-eof.xml oci-lob-erase.xml oci-lob-export.xml oci-lob-flush.xml oci-lob-import.xml oci-lob-load.xml oci-l
wez Tue Sep 6 15:59:37 2005 EDT Removed files: /phpdoc/en/reference/oci8/functions oci-lob-append.xml oci-lob-close.xml oci-lob-eof.xml oci-lob-erase.xml oci-lob-export.xml oci-lob-flush.xml oci-lob-import.xml oci-lob-load.xml oci-lob-read.xml oci-lob-rewind.xml oci-lob-save.xml oci-lob-seek.xml oci-lob-size.xml oci-lob-tell.xml oci-lob-truncate.xml oci-lob-write-temporary.xml oci-lob-write.xml Log: rename almost all oci-lob files to OCI-Lob
[PHP-DOC] cvs: phpdoc /en/reference/oci8/functions oci-collection-append.xml oci-collection-assign.xml oci-collection-element-assign.xml oci-collection-element-get.xml oci-collection-free.xml oci-coll
wez Tue Sep 6 15:53:03 2005 EDT Removed files: /phpdoc/en/reference/oci8/functions oci-collection-append.xml oci-collection-assign.xml oci-collection-element-assign.xml oci-collection-element-get.xml oci-collection-free.xml oci-collection-max.xml oci-collection-size.xml oci-collection-trim.xml Log: rename oci-collection-* to OCI-Collection-* (the latter were magically copied on the server side to preserve history)
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-quote.xml
And PDO::quote() does nothing for ODBC, because it currently has no idea what dialect of SQL is spoken by the underlying ODBC driver. --Wez. On 8/30/05, Dan Scott <[EMAIL PROTECTED]> wrote: > dbs Tue Aug 30 20:56:36 2005 EDT > > Modified files: > /phpdoc/en/reference/pdo/functions PDO-quote.xml > Log: > Emphasize the usefulness of prepared statements vs. quoted input. > > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-quote.xml?r1=1.2&r2=1.3&ty=u > Index: phpdoc/en/reference/pdo/functions/PDO-quote.xml > diff -u phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.2 > phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.3 > --- phpdoc/en/reference/pdo/functions/PDO-quote.xml:1.2 Mon Jul 11 00:38:55 > 2005 > +++ phpdoc/en/reference/pdo/functions/PDO-quote.xml Tue Aug 30 20:56:35 > 2005 > @@ -1,5 +1,5 @@ > > - > + > > > > @@ -24,9 +24,14 @@ > quoting style appropriate to the underlying driver. > > > - If you're using this function to build SQL, it is recommended that you > - using prepared statements and bound parameters instead, as it is not only > - more convenient, but often much faster. > + If you are using this function to build SQL statements, you are > + strongly recommended to use > + PDO::prepare to prepare SQL statements with bound > + parameters instead of using PDO::quote to interpolate > + user input into a SQL statement. Prepared statements with bound parameters > + are not only more portable, more convenient, and vastly more secure, but > + are often much faster than interpolating user input into slight variations > + on the same basic SQL statement. > > > Not all PDO drivers implement this method (notably PDO_ODBC). Consider >
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo ini.xml reference.xml
Just FYI, the general plan is to document driver specifics in their own sections of the manual. This is something that Dan and myself planned to sit down and work on at OSCON... but that didn't happen. --Wez. On 8/10/05, Jakub Vrana <[EMAIL PROTECTED]> wrote: > vrana Wed Aug 10 04:36:30 2005 EDT > > Added files: > /phpdoc/en/reference/pdoini.xml > > Modified files: > /phpdoc/en/reference/pdoreference.xml > Log: > ini options > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.26&r2=1.27&ty=u > Index: phpdoc/en/reference/pdo/reference.xml > diff -u phpdoc/en/reference/pdo/reference.xml:1.26 > phpdoc/en/reference/pdo/reference.xml:1.27 > --- phpdoc/en/reference/pdo/reference.xml:1.26 Sat Jul 30 02:35:15 2005 > +++ phpdoc/en/reference/pdo/reference.xml Wed Aug 10 04:36:30 2005 > @@ -1,5 +1,5 @@ > > - > + > > >PDO Functions > @@ -159,6 +159,9 @@ > > > > + > + &reference.pdo.ini; > + > > PDO Drivers > > > http://cvs.php.net/co.php/phpdoc/en/reference/pdo/ini.xml?r=1.1&p=1 > Index: phpdoc/en/reference/pdo/ini.xml > +++ phpdoc/en/reference/pdo/ini.xml > > > > &reftitle.runtime; > &extension.runtime; > > >PDO Configuration Options > > > > Name > Default > Changeable > Changelog > > > > > pdo.dsn.* > > &php.ini; only > > > > pdo_odbc.connection_pooling > "strict" > PHP_INI_ALL > > > > > > &ini.php.constants; > > > &ini.descriptions.title; > > > > > > pdo.dsn.* > string > > > > Defines DSN alias. See for > thorough explanation. > > > > > > > pdo_odbc.connection_pooling > string > > > > Whether to pool ODBC connections. Can be one of "strict", "relaxed" or > "off" (equals to ""). > > > > > > > > > >
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml reference.xml /en/reference/pdo/functions PDO-beginTransaction.xml PDO-construct.xml PDO-errorCode.xml PDO-errorInfo.xml PDO-exec.xml PDO-getAttr
wez Mon Jul 11 00:38:56 2005 EDT Modified files: /phpdoc/en/reference/pdoconstants.xml reference.xml /phpdoc/en/reference/pdo/functions PDO-beginTransaction.xml PDO-construct.xml PDO-errorCode.xml PDO-errorInfo.xml PDO-exec.xml PDO-getAttribute.xml PDO-lastInsertId.xml PDO-prepare.xml PDO-query.xml PDO-quote.xml PDO-rollBack.xml PDO-setAttribute.xml PDOStatement-bindColumn.xml PDOStatement-bindParam.xml PDOStatement-errorCode.xml Log: misc tweaks http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.7&r2=1.8&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.7 phpdoc/en/reference/pdo/constants.xml:1.8 --- phpdoc/en/reference/pdo/constants.xml:1.7 Tue Jul 5 16:09:17 2005 +++ phpdoc/en/reference/pdo/constants.xml Mon Jul 11 00:38:54 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -266,7 +266,9 @@ - + Setting the prefetch size allows you to balance speed against memory + usage for your application. Not all database/driver combinations support + setting of the prefetch size. @@ -370,6 +372,19 @@ + + + +PDO_ATTR_DRIVER_NAME + (string) + + + + Returns the name of the driver. + + + + PDO_ATTR_ORACLE_NULLS @@ -426,7 +441,7 @@ Do not raise an error or exception if an error occurs. The developer is - expected to explicitly check for errors. + expected to explicitly check for errors. This is the default mode. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.24&r2=1.25&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.24 phpdoc/en/reference/pdo/reference.xml:1.25 --- phpdoc/en/reference/pdo/reference.xml:1.24 Sat Jul 9 01:19:00 2005 +++ phpdoc/en/reference/pdo/reference.xml Mon Jul 11 00:38:54 2005 @@ -1,5 +1,5 @@ - + PDO Functions @@ -190,7 +190,7 @@ PDO_ODBC - ODBC v3 (IBM DB2 and unixODBC) + ODBC v3 (IBM DB2, unixODBC and win32 ODBC) PDO_PGSQL @@ -200,6 +200,10 @@ PDO_SQLITE SQLite 3.x + + sqlite + SQLite 2.x (PHP 5.1 and up) + http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml?r1=1.2&r2=1.3&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml diff -u phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.2 phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.3 --- phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml:1.2 Sat Feb 5 13:52:58 2005 +++ phpdoc/en/reference/pdo/functions/PDO-beginTransaction.xml Mon Jul 11 00:38:55 2005 @@ -1,5 +1,5 @@ - + @@ -17,9 +17,10 @@ &warn.experimental.func; - Turns off autocommit mode. Call PDO::commit or - PDO::rollback to end the transaction and return to - autocommit mode. + Turns off autocommit mode. While autocommit mode is turned off, changes + made to the database via the PDO object instance are not committed until + you end the transaction by calling either + PDO::commit or PDO::rollback. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-construct.xml?r1=1.11&r2=1.12&ty=u Index: phpdoc/en/reference/pdo/functions/PDO-construct.xml diff -u phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.11 phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.12 --- phpdoc/en/reference/pdo/functions/PDO-construct.xml:1.11Sun Feb 20 00:47:01 2005 +++ phpdoc/en/reference/pdo/functions/PDO-construct.xml Mon Jul 11 00:38:55 2005 @@ -1,5 +1,5 @@ - + PDO::__construct @@ -99,6 +99,22 @@ sqlite::memory: + + sqlite (version 2) + +sqlite2:/path/to/database +To create a database in memory, use: +sqlite2::memory: + + + The SQLite 2 PDO driver provides access to old SQLite 2 + databases that you may have created with earlier versions + of PHP. It is recommended that you migrate to SQLite 3 (the + PDO_SQLITE driver), as it has superior features and performance. + + + + http://cvs.php
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml /en/reference/pdo/functions PDO-lastInsertId.xml PDOStatement-closeCursor.xml
It's worth noting that calling closeCursor() is usually only required if you don't explicitly fetch all the rows from a given statement object before switching to a different statement object. In other words: $stmt->execute(); $stmt->fetch(); $stmt->execute(); will work happily, but $stmt->execute(); $stmt->fetch(); $otherStmt->execute(); might break with an out-of-sequence error for some drivers. Adding a $stmt->closeCursor() before $otherStmt->fetch() is one way to handle this situation. On 7/9/05, Dan Scott <[EMAIL PROTECTED]> wrote: > dbs Sat Jul 9 01:19:02 2005 EDT > > Added files: > /phpdoc/en/reference/pdo/functions PDOStatement-closeCursor.xml > > Modified files: > /phpdoc/en/reference/pdoreference.xml > /phpdoc/en/reference/pdo/functions PDO-lastInsertId.xml > Log: > PDO-lastInsertID() returns last value of sequence object. > Document PDOStatement-closeCursor(). > > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.23&r2=1.24&ty=u > Index: phpdoc/en/reference/pdo/reference.xml > diff -u phpdoc/en/reference/pdo/reference.xml:1.23 > phpdoc/en/reference/pdo/reference.xml:1.24 > --- phpdoc/en/reference/pdo/reference.xml:1.23 Fri Jun 3 08:54:13 2005 > +++ phpdoc/en/reference/pdo/reference.xml Sat Jul 9 01:19:00 2005 > @@ -1,5 +1,5 @@ > > - > + > > >PDO Functions > @@ -326,6 +326,12 @@ > > > > + closeCursor > + - closes the cursor, allowing the statement to be executed again > + > + > + > + > columnCount > - returns the number of columns in the result set > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml?r1=1.6&r2=1.7&ty=u > Index: phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml > diff -u phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml:1.6 > phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml:1.7 > --- phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml:1.6 Wed Mar 9 > 19:02:49 2005 > +++ phpdoc/en/reference/pdo/functions/PDO-lastInsertId.xml Sat Jul 9 > 01:19:01 2005 > @@ -1,11 +1,11 @@ > > - > + > > > > PDO::lastInsertId > > - Returns the ID of the last inserted row > + Returns the ID of the last inserted row or sequence value > > > > @@ -18,7 +18,7 @@ > &warn.experimental.func; > > > - Returns the ID of the last inserted row, or the next value from a > + Returns the ID of the last inserted row, or the last value from a > sequence object. > > > @@ -56,7 +56,7 @@ > > If a sequence name was specified for the name > parameter, PDOStatement::lastInsertId returns a > - string representing the next value retrieved from the specified sequence > + string representing the last value retrieved from the specified sequence > object. > > > > http://cvs.php.net/co.php/phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml?r=1.1&p=1 > Index: phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml > +++ phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml > > > > > > PDOStatement::closeCursor > >Closes the cursor, enabling the statement to be executed again. > > > > &reftitle.description; > >boolPDOStatement::closeCursor > > > > &warn.experimental.func; > > >PDOStatement::closeCursor frees up the connection >to the server so that other queries may be issued, but leaves the >statement in a state that enables it to be executed again. > > >This is implemented either as an optional driver specific method (allowing >for maximum efficiency), or as the generic PDO fallback if no driver >specific function is installed. > > >The PDO generic fallback is semantically the same as writing the following >code in your PHP script: > > > > > > > > > > > > > > > > > > &reftitle.seealso; > > > PDOStatement::execute > > > > > > > >
Re: [PHP-DOC] Re: [PHP-DEV] CVS Account Request: oriolm
I've created the module, the mailing list, hooked it up to the news server, created all the catalan accounts, updated the avail file and set up the cvs commits for the catalan module. All I did to create the catalan module was to copy the .cvsignore file from the phpdoc module. Bernat: although the module is there, please wait for Gabor to give you or the other guys the go-ahead, as it will make it easier for me to perform any other initialization for the translation project if you do. Goba: if you want something more clever doing (like copying files on the CVS server side) let me know precisely what you need before you give people the green light to commit. --Wez. On 6/19/05, Bernat <[EMAIL PROTECTED]> wrote: > Yes, these are the people, but I'll send two more people that were > waiting to apply for an account. And remember also my own one. > > Bernat > > On 6/19/05, Wez Furlong <[EMAIL PROTECTED]> wrote: > > OK, looks like we're going to set up a Catalan translation project. > > > > Gabor: > > Can you confirm that the country code for Catalan is CA, and that the > > module will be phpdoc-ca, and the mailing list will be > > [EMAIL PROTECTED] > > > > Bernat: > > The following people have applied for accounts to work on the translation: > > > > Aitor F. Vallespir Rivas, > > Marina Giralt Lladós > > Eduard Ereza MartÃnez > > Macià Falgà s > > Max Noé i Herrero > > Eduard Capell Brufau > > Oriol Morell > > > > I'll be activating the cvs module, mailing list and their accounts > > later today unless I hear otherwise from you guys. > > > > --Wez. > > > > > > On 6/15/05, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > > > Hi Wez, > > > > > > There seem to be some activity in starting a Catalan translation, but > > > unless at least one of these guys get an account, and a mailing list and > > > a cvs module is created, this is not possible to start. > > > > > > http://marc.theaimsgroup.com/?l=phpdoc&m=111601250906644&w=2 > > > > > > Goba > > > > > > > Are these requests legitimate or should we start blocking people > > > > mentioning catalan in cvs account requests? > > > > > > > > --Wez. > > > > > > > > On 6/14/05, Oriol Morell <[EMAIL PROTECTED]> wrote: > > > > > > > >>Member of the catalan translation > > > >> > > > >>-- > > > >>PHP Internals - PHP Runtime Development Mailing List > > > >>To unsubscribe, visit: http://www.php.net/unsub.php > > > >> > > > >> > > > > > > > > > > > > > > > > >
Re: [PHP-DOC] Re: [PHP-DEV] CVS Account Request: oriolm
On 6/19/05, Friedhelm Betz <[EMAIL PROTECTED]> wrote: > I am not Gabor, but yes, the *language code* for Catalan is ca. > Contry code ca is for Canada ;-) Gabor was in the Cc line, and language code is what I meant :)
Re: [PHP-DOC] Re: [PHP-DEV] CVS Account Request: oriolm
OK, looks like we're going to set up a Catalan translation project. Gabor: Can you confirm that the country code for Catalan is CA, and that the module will be phpdoc-ca, and the mailing list will be [EMAIL PROTECTED] Bernat: The following people have applied for accounts to work on the translation: Aitor F. Vallespir Rivas, Marina Giralt Lladós Eduard Ereza MartÃnez Macià Falgà s Max Noé i Herrero Eduard Capell Brufau Oriol Morell I'll be activating the cvs module, mailing list and their accounts later today unless I hear otherwise from you guys. --Wez. On 6/15/05, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > Hi Wez, > > There seem to be some activity in starting a Catalan translation, but > unless at least one of these guys get an account, and a mailing list and > a cvs module is created, this is not possible to start. > > http://marc.theaimsgroup.com/?l=phpdoc&m=111601250906644&w=2 > > Goba > > > Are these requests legitimate or should we start blocking people > > mentioning catalan in cvs account requests? > > > > --Wez. > > > > On 6/14/05, Oriol Morell <[EMAIL PROTECTED]> wrote: > > > >>Member of the catalan translation > >> > >>-- > >>PHP Internals - PHP Runtime Development Mailing List > >>To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > > > > >
[PHP-DOC] Re: [PHP-DEV] CVS Account Request: oriolm
Are these requests legitimate or should we start blocking people mentioning catalan in cvs account requests? --Wez. On 6/14/05, Oriol Morell <[EMAIL PROTECTED]> wrote: > Member of the catalan translation > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDO-lastInsertId.xml
Actually, it triggers an IM001 SQLSTATE error; whether that becomes an exception or not depends on your chosen error handling mode :-) --Wez. On Wed, 09 Mar 2005 23:29:35 -, Dan Scott <[EMAIL PROTECTED]> wrote: > + > + If the PDO driver does not support this capability, > + PDO::lastInsertID issues a PDOWarning exception. > > > >
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
That only handles statically compiled extensions. PHP doesn't know about dynamic dependencies yet. Besides, these docs are also for people running PHP 5.0.x and using the PECL extensions. On Thu, 10 Feb 2005 18:49:42 -, Nuno Lopes <[EMAIL PROTECTED]> wrote: > > Yep, stick them in ext and either load them from php.ini or through dl(). > > > > php_pdo.dll must be loaded before the other pdo dlls. > > > > Thanks :) > > > > --Wez. > > Shouldn't the new PHP 5.1 feature (that loads extensions by order) handle > that? > > Nuno > >
Re: [PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
Yep, stick them in ext and either load them from php.ini or through dl(). php_pdo.dll must be loaded before the other pdo dlls. Thanks :) --Wez. On Thu, 10 Feb 2005 18:31:16 + (GMT), Philip Olson <[EMAIL PROTECTED]> wrote: > > Does that point to http://snaps.php.net/win32/PECL_5_0/ ? > > Could it? > > It does now! Also, could you explain what Windows users need > to do with the other PDO DLL's? Like php_pdo_mysql.dll, > php_pdo_odbc.dll, etc. Just stick them in their ext folder > and calling on said DB will load them at runtime? > > Regards, > Philip > > > > On Thu, 10 Feb 2005 17:23:58 -, Philip Olson <[EMAIL PROTECTED]> wrote: > > > philip Thu Feb 10 12:23:58 2005 EDT > > > > > > Modified files: > > > /phpdoc/en/reference/pdoreference.xml > > > Log: > > > Also refer Windows users to snaps (for recent DLL) > > > > > > http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.16&r2=1.17&ty=u > > > Index: phpdoc/en/reference/pdo/reference.xml > > > diff -u phpdoc/en/reference/pdo/reference.xml:1.16 > > > phpdoc/en/reference/pdo/reference.xml:1.17 > > > --- phpdoc/en/reference/pdo/reference.xml:1.16 Wed Feb 9 23:30:50 2005 > > > +++ phpdoc/en/reference/pdo/reference.xml Thu Feb 10 12:23:58 2005 > > > @@ -1,5 +1,5 @@ > > > > > > - > > > + > > > > > > > > >PDO Functions > > > @@ -62,7 +62,8 @@ > > > > > > Windows users can download the extension DLL > > > php_pdo.dll > > > as part of the PECL collection binaries from > > > - &url.php.downloads;. > > > + &url.php.downloads; or a > > > more > > > + recent version from > > url="&url.php.snapshots;">&url.php.snapshots;. > > > > > > > > > > > > > > > >
[PHP-DOC] cvs: livedocs / build-ops.in build.sh configure.in mk_notes.php
wez Thu Nov 11 14:33:28 2004 EDT
Modified files:
/livedocs build-ops.in build.sh configure.in mk_notes.php
Log:
reinstate user-notes fetching via token
# grrr
http://cvs.php.net/diff.php/livedocs/build-ops.in?r1=1.10&r2=1.11&ty=u
Index: livedocs/build-ops.in
diff -u livedocs/build-ops.in:1.10 livedocs/build-ops.in:1.11
--- livedocs/build-ops.in:1.10 Sat Sep 11 08:22:44 2004
+++ livedocs/build-ops.in Thu Nov 11 14:33:26 2004
@@ -17,4 +17,5 @@
# LANGUAGES="en ar cs de es fi fr he hk hu it ja kr nl pl pt_BR ro ru sk sv tw
zh"
LANGUAGES="@LANGUAGES@"
[EMAIL PROTECTED]@
[EMAIL PROTECTED]@
http://cvs.php.net/diff.php/livedocs/build.sh?r1=1.25&r2=1.26&ty=u
Index: livedocs/build.sh
diff -u livedocs/build.sh:1.25 livedocs/build.sh:1.26
--- livedocs/build.sh:1.25 Sat Aug 14 17:34:05 2004
+++ livedocs/build.sh Thu Nov 11 14:33:27 2004
@@ -6,8 +6,10 @@
echo ""
-if test -n "$NOTES_MIRROR" ; then
+if test -n "$NOTES_MIRROR$NOTES_TOKEN" ; then
echo "Building user notes"
+ TOKEN=$NOTES_TOKEN
+ export TOKEN
${PHP} ${LIVEDOCSFORPHP}/mk_notes.php ${OUTPUTDIR} ${GENDIR}
${NOTES_MIRROR}
fi
http://cvs.php.net/diff.php/livedocs/configure.in?r1=1.28&r2=1.29&ty=u
Index: livedocs/configure.in
diff -u livedocs/configure.in:1.28 livedocs/configure.in:1.29
--- livedocs/configure.in:1.28 Sat Aug 14 17:34:05 2004
+++ livedocs/configure.in Thu Nov 11 14:33:27 2004
@@ -1,5 +1,5 @@
## A configure script
-## $Id: configure.in,v 1.28 2004/08/14 21:34:05 iliaa Exp $
+## $Id: configure.in,v 1.29 2004/11/11 19:33:27 wez Exp $
AC_PREREQ(2.13)
AC_INIT(livedoc.php)
@@ -87,6 +87,10 @@
[NOTES_MIRROR="$withval"],
[NOTES_MIRROR=""])
+AC_ARG_WITH(notes-token,[ --with-notes-token=TOKEN token to fetch user
notes],
+ [NOTES_TOKEN="$withval"],
+ [NOTES_TOKEN=""])
+
AC_ARG_WITH(web-base,[ --with-web-base[=DIR] Relative URL for
livedocs links [default=/]],
[WEBBASE="$withval"],
[WEBBASE="/"])
@@ -128,6 +132,7 @@
AC_SUBST(OUTPUTDIRFORPHP)
AC_SUBST(XSLTPROC)
AC_SUBST(NOTES_MIRROR)
+AC_SUBST(NOTES_TOKEN)
AC_OUTPUT(build-ops config.php .htaccess)
http://cvs.php.net/diff.php/livedocs/mk_notes.php?r1=1.4&r2=1.5&ty=u
Index: livedocs/mk_notes.php
diff -u livedocs/mk_notes.php:1.4 livedocs/mk_notes.php:1.5
--- livedocs/mk_notes.php:1.4 Wed Aug 18 16:56:57 2004
+++ livedocs/mk_notes.php Thu Nov 11 14:33:27 2004
@@ -19,7 +19,7 @@
// | livedocs.|
// +--+
//
-// $Id: mk_notes.php,v 1.4 2004/08/18 20:56:57 iliaa Exp $
+// $Id: mk_notes.php,v 1.5 2004/11/11 19:33:27 wez Exp $
$create = <
[PHP-DOC] cvs: livedocs / build-ops.in
wez Thu Nov 11 14:46:01 2004 EDT Modified files: /livedocs build-ops.in Log: Fix name http://cvs.php.net/diff.php/livedocs/build-ops.in?r1=1.11&r2=1.12&ty=u Index: livedocs/build-ops.in diff -u livedocs/build-ops.in:1.11 livedocs/build-ops.in:1.12 --- livedocs/build-ops.in:1.11 Thu Nov 11 14:33:26 2004 +++ livedocs/build-ops.in Thu Nov 11 14:46:01 2004 @@ -17,5 +17,5 @@ # LANGUAGES="en ar cs de es fi fr he hk hu it ja kr nl pl pt_BR ro ru sk sv tw zh" LANGUAGES="@LANGUAGES@" [EMAIL PROTECTED]@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@
[PHP-DOC] Re: Mailing CVS commits
The lists box appears to be having a problem; we are on the case. --Wez. Jakub Vrana wrote: Hello! It seems that sending e-mails for CVS commits are temporarily unavailable. When I commit something to phpdoc, commit is successful but no mail to the list is sent. This is what CVS says: Checking in check-references.php; /repository/phpdoc/scripts/check-references.php,v <-- check-references.php new revision: 1.6; previous revision: 1.5 done (about 70 seconds of silence) Mailing the commit email to [EMAIL PROTECTED] connect 216.92.131.4:25 failed at /repository/CVSROOT/loginfo.pl line 260. It worked today at 13:20 GMT yet but doesn't work at this moment. Jakub Vrana
Re: [PHP-DOC] Livedocs CVSTrac?
Well, only one I know of (from first-hand experience today :-/) --Wez. On Tue, 17 Aug 2004 12:02:34 -0400, Sean Coates <[EMAIL PROTECTED]> wrote: > Well, wanted to see what others thought, before taking it to [EMAIL PROTECTED] > > Seems there are a number of cvstrac vulnerabilities.. that's not good. > > S > > > > Gabor Hojtsy wrote: > >> Opinions? > > > > Fine with me. You need to convince systems@ about this anyway :) > > > > Goba >
Re: [PHP-DOC] Livedocs Status?
Instead of non-specific "head is broken" email, why not point out what is broken? Livedocs is running fine here; I built it only a week or so ago with no problems. Plus, I have a mirror that updates daily (livedocs.thebrainroom.net) with no problems (assuming that someone hasn't broken phpdoc) If you have a patch that works properly, by all means send it our way (either myself, Ilia, Derick or Goba). What we don't want is a half-baked patch that "fixes" stuff for one person/case and that breaks everything else; and that is the reason we tightened up the karma--some of us are *already* running livedocs in production. I've seen plenty of people say that livedocs isn't ready, but non of them have said why or come up with a firm list of what needs to be done to make it ready, let alone come up with patches for that. We've already said that if a steady stream of good patches come in, more karma can be granted. It's OpenSource: hack, send in patches. --Wez. PS: no need to pgp sign messages to a mailing list... On Sat, 14 Aug 2004 10:59:51 -0400, Sean Coates <[EMAIL PROTECTED]> wrote: > [This is a follow-up post to my previous post, "Livedocs woes".] > > What is the current status of livedocs development? > > My understanding is that anyone with phpdoc karma, also, once, had > livedocs karma. A commit was made that some maintainers did not like, > and karma was removed, and only granted to certain people (Currently: > iliaa,goba,wez,derick,sfox,alan_k). Please correct me if I am wrong. > > There are several outstanding issues with the livedocs code. As I said > in my post, last night, HEAD seems broken. Also, Nuno has a number of > patches available at http://livedocs.aborla.net/ > > My point? I'd like to determine the proper procedure for patching > (getting patches approved for) livedocs, or find an alternative > development method. > > I realize that livedocs is not ready for production, as it is intended. > It is, however VERY useful for doc team members (see Philip's posts re: > CHANGELOG and the EXIF changes he made for a practical example). > > I also understand that the original authors of livedocs don't want their > code messed with. Isn't this the beauty of CVS, though? > > I suspect this idea won't be well-received, but if we're not > willing/able to keep livedocs HEAD up to date, could we not branch the > module for testing purposes? Karma could be re-granted on a per-case > basis, with the condition that non-core developers do not commit to > HEAD, but to the dev branch. My understanding of the "staleness" of > livedocs is that Ilia and Wez are busy on PHP 5. I understand this. > People like Nuno, though, have demonstrated a knowledge of livedocs > code, and should be able to contribute, IMHO. I'd also like to see > livedocs tagged regularly so we can easily "rollback" to a previous > version (last night, while getting livedocs running, and failing > miserably, I was tempted to start pulling random dates out for cvs up -D ). > > I'm not trying to point fingers, here, I'd just like to see livedocs > move forward. Can we find a way to make this happen? > > > > S
Re: [PHP-DOC] Not an active author?
+1 for a big list of all contributors Ranking/Rating is like measuring and comparing penis size. It's meaningless for the majority of people reading the docs and serves only as an ego boost for the *ahem* big committers and inspires penis envy in the not-so-big committers. We don't really need that in OpenSource :-) --Wez. On Thu, 12 Aug 2004 18:56:10 + (GMT), Philip Olson <[EMAIL PROTECTED]> wrote: > > How about this, have that list include the people on the > frontpage and simply title it: > > Contributors to the PHP Manual > > Inactive or not, all of these people are contributors. Sure > some people will be listed in both places but not many. > > Regards, > Philip > > > > > On Thu, 12 Aug 2004, Gabor Hojtsy wrote: > > > So, allow users to opt out of the "inactive" page. > > Would that solve the problem? > > >>> > > >>>Or better word it so that it does not indicate that the listed people > > >>>are *completely* inactive currently. > > >> > > >>Just remove this whole section. > > > > > > s/section/pthrase I mean > > > > > > Especially this part looks bad: > > > Authors and Editors > > > > > > Although not active currently, the following contributors made a big > > > impact with adding content to the manual previously: > > > > Well, once again I am not much proficient in politics, and all this > > crediting stuff evolves around politics. Since noone else took up the > > job of crediting current contributors, someone needed to do so. Since I > > am not a native English speaker, I might have used wording which is > > offensive. The points I tried to summarise into the short sentences on > > the contributions page are: > > > >- those listed on the frontpage are definitely *not the only* > > valuable people, but those who are currently *most active* > > > >- those listed on the frontpage plus those listed on the > > contributors page are *still not the only* valuable > > people, but those, who have been the most busy people > > around phpdoc still its beginning > > > >- there are still more people who we not list, but provided > > valuable stuff (heck, even the unnamed manual user note > > submitters are thanked for their work!) > > > > I mean that we look positively on all the people we have listed, and we > > even look positively on those people who have not been possible to > > include in those lists. Just for the manual to be accurate and actual, > > we need to have active people who fix bugs, add new function > > documentations, etc. And PHP being actively developed and bugfixed, and > > outdated - albeit proficiently written - documentation does not help > > users much, we need people to be *active*. We need lots of activity, > > since we have a lot of tasks to do. Those listed on the frontpage are > > the most active, although the actives are not limited to those. > > > > I would appreciate if someone with better English skills would reword > > those entities, so they fit into the positive image the whole crediting > > is supposed to be under. > > > > BTW there are some people getting active very recently, like Sean Coates > > or Dave Barr, although they have no such problem as being listed as > > 'inactives', since they have not contributed such an invaluable amount > > of value to the manual like you Sara (which entitled you to be listed). > > > > Goba > > >
Re: [PHP-DOC] windows install
if I get time, it will be ported to 5.0.1. The .reg file that registersyslog generates will also be included in the distro, but set up assuming that the user will install to C:\php5; so docs will need to tell the user to edit that .reg file if they are putting it elsewhere. Phil said he was going to adjust the installer to handle this automatically, but I haven't heard from him in a week. --Wez. On Sun, 8 Aug 2004 20:55:40 +0100, Nuno Lopes <[EMAIL PROTECTED]> wrote: > Uhm, sorry.. Only now I realised that the script has a $dll=$argv[1]; line > :) > > So, I have to call the script with 'php registersyslog.php > C:\\php\\php5ts.dll'. > > Another thing: will this file be bundled in the windows packages? If yes I > can add this to the docs. > Do this works in PHP 4 and PHP 5.0, or is a PHP 5.1 only feature? > > Nuno > > > > - Original Message - > > Doesn't sound like you really have the keys in the right place, or you > > don't have the php5ts.dll in the place that the key points to. > > > > I added a .reg file the other day that should work, although I didn't > > test it (was on linux at the time). > > > > --Wez. > >
Re: [PHP-DOC] windows install
Doesn't sound like you really have the keys in the right place, or you don't have the php5ts.dll in the place that the key points to. I added a .reg file the other day that should work, although I didn't test it (was on linux at the time). --Wez. On Sun, 8 Aug 2004 13:27:32 +0100, Nuno Lopes <[EMAIL PROTECTED]> wrote: > > Also note that an ancient syslog() bug on windows has been resolved in > > the last couple of days that requires a couple of registry keys to be > > created at installation time (but only if you want nice clear syslog > > output in your event log). > > > > I'll send you more details in a day or so (or you can peek at > > php-src/win32/build/registersyslog.php) > > > > --Wez. > > > Hello Wez, > > I've added the entries to the registry (stated in the registersyslog.php > file) but it seems to don't work. > > The EventViewer continues to have some garbage in each message: > > Event Type: Information > Event Source: PHP-5.1.0-dev > Event Category: (6) > Event ID: 2 > Description: > The description for Event ID ( 2 ) in Source ( PHP-5.1.0-dev ) cannot be > found. The local computer may not have the necessary registry information or > message DLL files to display messages from a remote computer. You may be > able to use the /AUXSOURCE= flag to retrieve this description; see Help and > Support for details. The following information is part of the event: > php[2764]; PHP Notice: Undefined offset: 1 in c:\cvs\xx.php > > Nuno >
Re: [PHP-DOC] windows install
No, this only affects the fall-back php.ini file location, and does
not solve the DLL linkage issues.
--Wez.
On Thu, 5 Aug 2004 00:36:49 +0200, Friedhelm Betz <[EMAIL PROTECTED]> wrote:
> > According to what you said I expect changes to
> > main/config.w32 .h and win32/build/config.w32.h.in to _not_ make use of
> >
> > #define PHP_CONFIG_FILE_PATH (getenv("SystemRoot"))?getenv("SystemRoot"):""
> >
> > for default path/directories
> > Instead it should use something like "c:\\php5" or "c:\\php4 as default
> > location.
> > Changing this would have the benefit, that we could instruct people to use
> > the default location c:\php4 or c:\php5 and they do not need to use PATH or
> > PHPRC, right?
Re: [PHP-DOC] windows install
Thou shalt not put application data into SYSTEMROOT. Don't do it. Ever. Really! Read the M$ guidelines on this stuff, including the dll-hell articles and the setup and install guidelines. Read the documentation on .ini files and the registry. They've all been telling developers to keep their crap out of the system folders; they don't belong there. Do *NOT* tell our newbie users to put stuff in there, because they invariably screw things up during installation, uninstallation and upgrade time. It's a big headache. Let's not go there. --Wez. On Mon, 2 Aug 2004 20:54:15 +0200, Friedhelm Betz <[EMAIL PROTECTED]> wrote: > I thought about twice and I wonder why it is preferable to use PHPRC instead > just copy php-(sapiname).ini to SYSTEMROOT? > > Using PHPRC is indeed nice but seems to be a superfluous hurdle for newbies. > We do not talk about 'copy dlls' just one/two ini-files to SYSTEMROOT. Nothing > wrong with that, IMHO.
Re: [PHP-DOC] windows install
> Uhm, copying the php.ini file to the windows folder isn't that bad. (as it
> isn't updated)
Yes it is :)
Don't do it :)
Ini files in the windows folder have been a strongly deprecated
practice since win95 and the registry emerged.
php-{sapi}.ini is the best practice, and keep it out of a global
location to avoid collisions with installations of other versions of
PHP.
> I haven't explained how to set PHPRC, because I think it doesn't worth it.
> I've just used the PHPIniPath registry setting.
You should document PHPRC too as it is more portable and users might
not have rights to edit the registry on multi-user win32 servers.
--Wez.
Re: [PHP-DOC] windows install
> 3. Planning for the future, I have also added an internal > link on the ActiveScript engine stuff, so we can document > how can it be registered as a Windows Scripting Host > provider, and used for scripting. That is a short and easy > to write part and should be included in the Windows install > section (see the readme in the actionscript php source). Note that this has moved to PECL as of PHP 5.0.1 and the ProgId changed (damned registered trademarks!). Also note that an ancient syslog() bug on windows has been resolved in the last couple of days that requires a couple of registry keys to be created at installation time (but only if you want nice clear syslog output in your event log). I'll send you more details in a day or so (or you can peek at php-src/win32/build/registersyslog.php) --Wez.
Re: [PHP-DOC] cvs: phpdoc /en/reference/stream constants.xml /en/reference/stream/functions stream-socket-accept.xml stream-socket-server.xml
> > PHP 5.1 will include a new function "stream_socket_listen" that will > > allow you manually listen(). The rationale for that is that you might > > want to alter some socket settings before actually accepting > > connections. Currently, there aren't any of these to configure, so it > > is low priority. > > Was this already added? not yet. > > The UDP example reads only a single byte; check the specs for the > > daytime protocol to see how much it should read; if it isn't reading > > enough, that script might break. > > Quote (http://www.faqs.org/rfcs/rfc867.html): > "UDP Based Daytime Service >Another daytime service service is defined as a datagram based >application on UDP. A server listens for UDP datagrams on UDP port >13. When a datagram is received, an answering datagram is sent >containing the current date and time as a ASCII character string (the >data in the received datagram is ignored)." > > Uhm, I think 1 byte is enough? Then is is worth noting the following in the recvfrom docs (excerpt from recvfrom(2)): If a message is too long to fit in the supplied buffer, excess bytes may be discarded depending on the type of socket the message is received from. This applies to datagram orientated sockets. --Wez.
Re: [PHP-DOC] cvs: phpdoc /en/reference/stream constants.xml /en/reference/stream/functions stream-socket-accept.xml stream-socket-server.xml
Hey Nuno, A couple of comments: The LISTEN flag is used to actually "switch-on" a connection-orientated transport (eg: TCP) so that it can accept connections. So that sentence should read something like: "Connection-orientated transports (such as TCP) must use this flag, otherwise the server socket will not be enabled. Using this flag for connect-less transports (such as UDP) is an error." PHP 5.1 will include a new function "stream_socket_listen" that will allow you manually listen(). The rationale for that is that you might want to alter some socket settings before actually accepting connections. Currently, there aren't any of these to configure, so it is low priority. Rather than saying "this function doesn't work with UDP sockets", you should say "it is an error to use this function with UDP sockets", because the function itself isn't broken or deficient; using it with UDP sockets is an error in your code. The UDP example reads only a single byte; check the specs for the daytime protocol to see how much it should read; if it isn't reading enough, that script might break. --Wez. On Sat, 31 Jul 2004 11:48:38 -, Nuno Lopes <[EMAIL PROTECTED]> wrote: > nlopess Sat Jul 31 07:48:38 2004 EDT > > Modified files: > /phpdoc/en/reference/stream constants.xml > /phpdoc/en/reference/stream/functions stream-socket-accept.xml > stream-socket-server.xml > Log: > fix #27211: clarify how to use UDP server sockets > #please review this > > http://cvs.php.net/diff.php/phpdoc/en/reference/stream/constants.xml?r1=1.10&r2=1.11&ty=u > Index: phpdoc/en/reference/stream/constants.xml > diff -u phpdoc/en/reference/stream/constants.xml:1.10 > phpdoc/en/reference/stream/constants.xml:1.11 > --- phpdoc/en/reference/stream/constants.xml:1.10 Fri May 21 11:20:48 2004 > +++ phpdoc/en/reference/stream/constants.xmlSat Jul 31 07:48:38 2004 > @@ -1,5 +1,5 @@ > > - > + > > &reftitle.constants; > &extension.constants; > @@ -95,7 +95,7 @@ >STREAM_SERVER_LISTEN * >Tells a stream created with stream_socket_server > and bound using the STREAM_SERVER_BIND flag to start > - listening on the socket. Server sockets should always include this flag. > + listening on the socket. TCP Server sockets should always include this flag. > > > > http://cvs.php.net/diff.php/phpdoc/en/reference/stream/functions/stream-socket-accept.xml?r1=1.2&r2=1.3&ty=u > Index: phpdoc/en/reference/stream/functions/stream-socket-accept.xml > diff -u phpdoc/en/reference/stream/functions/stream-socket-accept.xml:1.2 > phpdoc/en/reference/stream/functions/stream-socket-accept.xml:1.3 > --- phpdoc/en/reference/stream/functions/stream-socket-accept.xml:1.2 Thu Apr 1 > 01:31:14 2004 > +++ phpdoc/en/reference/stream/functions/stream-socket-accept.xml Sat Jul 31 > 07:48:38 2004 > @@ -1,5 +1,5 @@ > > - > + > > > stream_socket_accept > @@ -31,6 +31,13 @@ > > If the call fails, it will return &false;. > > + > + > + This function doens't work with UDP server sockets. Use > + stream_socket_recvfrom and > + stream_socket_sendto instead. > + > + > > See also stream_socket_server, > stream_socket_get_name, > http://cvs.php.net/diff.php/phpdoc/en/reference/stream/functions/stream-socket-server.xml?r1=1.15&r2=1.16&ty=u > Index: phpdoc/en/reference/stream/functions/stream-socket-server.xml > diff -u phpdoc/en/reference/stream/functions/stream-socket-server.xml:1.15 > phpdoc/en/reference/stream/functions/stream-socket-server.xml:1.16 > --- phpdoc/en/reference/stream/functions/stream-socket-server.xml:1.15 Wed Jun 16 > 09:01:22 2004 > +++ phpdoc/en/reference/stream/functions/stream-socket-server.xml Sat Jul 31 > 07:48:38 2004 > @@ -1,5 +1,5 @@ > > - > + > > > stream_socket_server > @@ -32,6 +32,12 @@ > combination of socket creation flags. The default value of flags is > STREAM_SERVER_BIND | > STREAM_SERVER_LISTEN. > > + > + > + For UDP sockets, you must use STREAM_SERVER_BIND as > + the flags parameter. > + > + > > This function only creates a socket, to begin accepting connections > use stream_socket_accept. > @@ -59,7 +65,7 @@ > > > > - stream_socket_server Example > + Using TCP server sockets > > > > >
Re: [PHP-DOC] wider look on crediting at php.net projects
The CREDITS etiquette for php extensions isn't quite what you describe here. The accepted practice (there are no rules) is this: If you have the karma and have made some contribution(s), and you feel that it was worthwhile, you simply add yourself to the CREDITS file for the relevant extension. If you're unsure, you will usually ask someone else that is listed there if it would be okay to be added. If other people disagree, an argument^H^H^H^H^H^Hdiscussion will ensue to resolve the matter. (this has not ever happened, AFAIK) IMO, it would be nice to extend this idea to phpdoc and have some kind of author tags per file in the doc tree and allow the authors/translators to use them to credit themselves. --Wez. On Wed, 21 Jul 2004 12:45:37 +, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > PHP itself. See your phpcredits() page, I use the > php.net/credits page for reference. I have picked the > MySQL extension as the prime example. Look at the table: > >MySQL : Zeev Suraski, Zak Greant, Georg Richter > > Is this to beleive? I guess noone doubts that this is > far from a complete list of the MySQL extension contributors > and authors. > If you watch closely, you see two distinct approaches here. One is to > credit *only the first* defining people behind some entity (PHP itself > and smarty are examples for this approach). The PEAR, PECL and PHP > website approach seems to be to credit *only the active* people behind > the projects (thus the concept of maintainer comes to existance). The > PHP source code approach (Andi and Zeev are the authors and maintainers > of PHP, Alexander Aulbach, et.al. are the authors of the manual and > stuff) is under attack by some people.
Re: [PHP-DOC] I have uptodate commiter stats
On Mon, 19 Jul 2004 18:10:59 -0400 (EDT), Adam Maccabee Trachtenberg > We have a "PHP Group" that we somehow manage to determine from our > list of contributors. Ah, but that's different thing; the PHP Group isn't (necessarily) comprised of people writing PHP, instead it's more of a group of people steering PHP. > I don't see why the "PHP Documentation Team" > section on phpinfo() can't be similarly selected by some magical > community agreement. I certainly wouldn't object to that, and there are a number of people, the phpdoc "regulars", that would get my vote to become the phpdoc equivalent of the PHP group, and be listed there in phpcredits(), but that is different from being "just" an author of the documentation and being credited as such. --Wez.
Re: [PHP-DOC] I have uptodate commiter stats
> We have gone through this conversation several times. All people means > even people with one commit? Yes, because that one commit is a contribution. Sure, people make mistakes, but so what, really? > If we list all people, do we list editors > on the frontpage (exactly like PEARdoc does)? Who are editors? They need > to be picked by hand, no? If we list all people, who we list on the > phpcredits() page? Noone? All people do not fit there. Then credit them as a "cast of hundreds" and make it link to the list in the back of the manual. My point is that it is a waste of time trying to track down just "how much" to credit someone; everyone that contributed, contributed. If you really want to rank them, do it in reverse order of commits, but you should still list them all. > The idea of crediting current authors a bit more is to encourage them to > stay here. And having your name among the 200 or so people in the world that contributed to what is probably one of the most widely spread pieces of online documentation isn't enough? :-) I think it is a testament to the PHP manual that so many have contributed to make it what it is, why not list them all? > They make up the small list which we can put into > phpcredits(). Ah, now I see the motivation. It's a tricky proposition. There is no fair way really to credit without crediting all involved parties, IMO, and that would be too long a list. > If we go with the long list, current contributors will not > get more credit then those whose content was probably replaced or > overedited by the currently active team. What I don't like about that sentence is "get more credit" and "probably replaced". Anyway, I don't have particularly strong feelings about what does or does not happen, I just wanted to point out that I don't think ranking based on an arbitrary cut-off point in CVS commits is really all that fair (for instance: one person documents a new extension in great detail and commits it but doesn't get higher than the bottom of the list; is it fair on them to not be credited?), and can't see a practical fair solution short of listing everyone that contributed. So, having given my opinion, I'll withdraw and let you get on ;-) --Wez.
Re: [PHP-DOC] I have uptodate commiter stats
Why not just stick a big list of all contributors in there for now, and work towards crediting per page? Seems like a sensible balance between overall fairness and overall work; why expend huge effort on the credits section when there is plenty of other stuff to be getting on with. I don't think any kind of filtering on the list of committers will lead to satisfactory results without someone to audit everything ever done by everyone (just MHO), so I see it as a maintainance task with no real benefits compared to listing all people (you already have the list). --Wez. On Mon, 19 Jul 2004 20:47:54 +, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > Wez, Dave, Philip, and others, > > The idea behind generating an author list to start with was to get > somewhere forward in the process. As I have said I have provided a list > for discussion. And as I have also said, - apart from two people - the > current "top list" contains names I think the community recognize and > see their contributions as valuable ones. I have also said the list is > open for additions, so "the number mark" was just some guiding piece to > start the discussion, it is actually not some hard stuff I would like to > stick to. > > Sure it would be nicer to credit people by section. BUT to make that > possible, we need to start collecting per section credit names and need > to fill in holes in the system (credit previous work). This is obviously > more work then we are currently able to handle, given that we have > enough stuff with the install part, oop5 section and stuff. We would > also need to have our rendering systems adopted to such a crediting > scheme. DSSSL, XSLT and livedocs all need more work on them to support > this as far as I see, since we use all of these methods currently > (DSSSL, XSLT), or we are going to use them (livedocs) in the future. > > The current situation (years old list of currently inactive authors, and > no credit for current hard workers) is not something that should be > kept. The ideal situation is not something we have volunteers to do. Now > what can we choose? An intermediate solution. This is what I have > offered. I have presented a list for discussion. Now I think it is a lot > easier to produce a list which is much better then the current situation > and will fit (with continual review) until someone volunteers to build > the base for the more fair solution we decided to use on the long run. > > Or do you think it is better to stick to a conceptually better solution > which noone seems to volunteer to build in a reasonble timeframe? Is it > better to direct any people to work on such a supporting system instead > of directing them to fix docbugs or to work on the oop5 section, or > elsewhere? > > Goba >
Re: [PHP-DOC] I have uptodate commiter stats
Hmm, isn't it better to credit the major authors per page/section? It seems somewhat arbitrary to say "the most commits in the last year gets you on the front page". What if your contributions are good enough to remain the same over several years; does your name drift out of the manual? What if you're the author of a popular section of the manual, but never touched anything else? What of people that make large contributions to a small section? Are they fairly represented? To me, it seems fairest to credit authors per page, and have a complete list of all contributors (no matter how small) in the front (or the back; there are nearly 300 people in your list). If you must, you can list those in descending order of "commit counts", but alphabetical seems fair to me. --Wez. On Sun, 18 Jul 2004 14:37:52 +, Gabor Hojtsy <[EMAIL PROTECTED]> wrote: > > http://goba.hu/commiters.html (beware 376 Kbyte html file!) > > Additionaly to this, here is the data of how many commits people had in > the last half year (since january 1 actually) (with only those CVS > accounts who had at least one commit). > > I propose we put a line above baoengb and add the people above it to the > frontpage authors list (this is nearly the same as the magic 100 mark we > use). I exclude baoengb here, because I know he achieved this high > commit number mostly by adding translated stuff to the EN tree, and then > reverting (multiple times AFAIR). Others are mostly respected people > here AFAIK, and they deserve to be listed as top authors. Dave is > someone to think about a bit, as he mostly achieved a top commiter > rating by mass fixing small mistakes (html->HTML, php->PHP, PHP3->PHP 3, > and such). > > Still I keep suggesting that the historical author list should contain > people above the 100 commit mark from the list presented at the URL > above (with a bit of human correction if needed). > > Funny that I am just above the line :)) > > OK, now provide your suggestions! > > +---+--+ > | didou | 1291 | - Mehdi Achour > | nlopess | 573 | - Nuno Lopes > | georg | 245 | - Georg Richter > | betz | 244 | - Friedhelm Betz > | tony2001 | 243 | - Antony Dovgal > | dave | 233 | - Dave (? - mostly done search&replace) > | vrana | 219 | - Jakub Vrana > | dams | 194 | - Damien Seguy > | irchtml | 189 | - Kenneth Schwartz > | goba | 172 | - Gabor Hojtsy > > +===+==+ (suggested crediting mark) > > | baoengb | 106 | > | wez | 64 | > |derick | 58 | > | moriyoshi | 44 | > |mg | 41 | > | pollita | 37 | > | progcom | 34 | > | vincent | 31 | > |kennyt | 28 | > |et | 26 | > | yannick | 21 | > |philip | 19 | > | derek | 18 | > | hholzgra | 14 | > | sean | 13 | > | dickmeiss | 11 | > | ali |8 | > | abies |6 | > | jan |5 | > | thetaphi |4 | > | samesch |4 | > | helly |4 | > | gui |4 | > | vlad |4 | > | curt |3 | > |mj |3 | > | stas |3 | > | cucinato |3 | > |andrei |3 | > | alindeman |3 | > | jdonagher |2 | > | hirokawa |2 | > | joey |2 | > |leszek |2 | > | conni |1 | > | poz |1 | > |ae |1 | > |rasmus |1 | > | amt |1 | > | hakan |1 | > |rioter |1 | > |nathan |1 | > | jsjohnst |1 | > | cece |1 | > |sp |1 | > +---+--+ >
RE: [PHP-DOC] Re: livedocs bug
Keep in mind that the database paths should be relative to PHPDOC so that the database can be rsync'd to other machines and deployed there. It does indeed sound like a win32 specific buglet. --Wez. > -Original Message- > From: Nuno Lopes [mailto:[EMAIL PROTECTED] > Sent: 28 May 2004 22:06 > To: [EMAIL PROTECTED]; PHPdoc > Subject: [PHP-DOC] Re: livedocs bug > > > I don't see this problem on *nix, could it be that it is > win32 specific? > > > > Ilia > > > Maybe, I'm using windows... > > There was already, a long time ago, a win specific problem > because you were > mixing '/' and DIRECTORY_SEPARATOR. (but I think I've fix it). > > If nobody fixes it, maybe tomorow I may take a look into this bug. > > Nuno > >
RE: [PHP-DOC] cvs: phpdoc /en/reference/openssl reference.xml
Please also add: You are STRONGLY encouraged to use the most recent OpenSSL version otherwise your web server could be vulnerable to attack. > In order to use the OpenSSL functions you need to > install theurl="&url.openssl;">OpenSSL package. > - PHP-4.0.4pl1 requires OpenSSL >= 0.9.6, but > PHP-4.0.5 and greater > - will also work with OpenSSL >= 0.9.5. > + PHP between versions 4.0.5 and 4.3.1 will work with > OpenSSL >= 0.9.5. > + Other versions (PHP <=4.0.4pl1 and >= 4.3.2) > require OpenSSL >= > + 0.9.6. > > > >
[PHP-DOC] cvs: livedocs / style_mapping.php
wez Wed May 26 11:40:04 2004 EDT
Modified files:
/livedocs style_mapping.php
Log:
little hack so asp code doesn't look stupid
(look at ref.com)
http://cvs.php.net/diff.php/livedocs/style_mapping.php?r1=1.17&r2=1.18&ty=u
Index: livedocs/style_mapping.php
diff -u livedocs/style_mapping.php:1.17 livedocs/style_mapping.php:1.18
--- livedocs/style_mapping.php:1.17 Tue May 25 16:15:03 2004
+++ livedocs/style_mapping.php Wed May 26 11:40:04 2004
@@ -18,7 +18,7 @@
// | Helper functions for formatting elements |
// +--+
//
-// $Id: style_mapping.php,v 1.17 2004/05/25 20:15:03 iliaa Exp $
+// $Id: style_mapping.php,v 1.18 2004/05/26 15:40:04 wez Exp $
// almost XPATH.. ;-)
$map = array(
@@ -310,6 +310,7 @@
}
switch ($node->attributes['role']) {
+ case 'asp':
case 'php':
// Small hack because highlight_string has changed its behaviour in PHP 5 RC1
if (version_compare(phpversion(), '5.0.0RC1') == -1){
[PHP-DOC] cvs: phpdoc /en/reference/openssl/functions openssl-pkcs7-sign.xml
wez Wed May 26 11:09:21 2004 EDT
Modified files:
/phpdoc/en/reference/openssl/functions openssl-pkcs7-sign.xml
Log:
fix it a little
http://cvs.php.net/diff.php/phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xml?r1=1.12&r2=1.13&ty=u
Index: phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xml
diff -u phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xml:1.12
phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xml:1.13
--- phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xml:1.12 Sat Feb 28
10:13:38 2004
+++ phpdoc/en/reference/openssl/functions/openssl-pkcs7-sign.xmlWed May 26
11:09:21 2004
@@ -1,5 +1,5 @@
-
+
@@ -60,9 +60,9 @@
fclose($fp);
// encrypt it
if (openssl_pkcs7_sign("msg.txt", "signed.txt", "mycert.pem",
-array("mycert.pem", "mypassphrase"),
+array("file://mycert.pem", "mypassphrase"),
array("To" => "[EMAIL PROTECTED]", // keyed syntax
- "From" => "HQ <[EMAIL PROTECTED]>", // indexed syntax
+ "From: HQ <[EMAIL PROTECTED]>", // indexed syntax
"Subject" => "Eyes only")
)) {
// message signed - send it!
[PHP-DOC] cvs: livedocs / livedoc_funcs.php
wez Wed May 26 05:25:52 2004 EDT
Modified files:
/livedocs livedoc_funcs.php
Log:
Fix overtuning.
Patch by Jakub Vrana
# ps: Jakub, please Cc: ilia directly if you spot another thing like this,
# as he is not subscribed to phpdoc@
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.4&r2=1.5&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.4 livedocs/livedoc_funcs.php:1.5
--- livedocs/livedoc_funcs.php:1.4 Tue May 25 16:15:03 2004
+++ livedocs/livedoc_funcs.php Wed May 26 05:25:52 2004
@@ -330,7 +330,7 @@
$func_name = str_replace('-', '_', $parts[4]);
$stag = "xref linkend=\"$id\"";
$etag = "xref";
- } else if (isset($parts[3])) {
+ } else if (isset($parts[3]) && !isset($parts[4])) {
$id = 'function.' . $parts[3];
$func_name = lookup_title($id);
} else {
RE: [PHP-DOC] restructuring the install section
> > + Unixy Systems > > + Apache > > + ... > > + Windows > > + Apache > > + IIS 6 (Win2k3) > > + IIS 5 (Win2k / WinXP) > > + ... > > The problem is that the different Unix variants have different > instructions for Apache: HP-UX, Solaris, MacOSX. How do you > think that > could fit in here? I don't know myself therefore I ask :) Are they really all that different? If it's just a few minor differences, then those things can be noted as subsections of the server docs: + Unixy + Apache + HP-SUX + Slowaris Etc ;) If there are a large number of differences for a given platform across the different servers, it might well be worth giving that platform a section of it's own at the same level as unix and windows docs. > Great. I planned to ask people to review the docs, as I also find it > silly to move stuff to the system folder, while it will work > without it. > Also if the php.ini can be found in the php.exe folder in the first > place, why not tell people to put it there? It would be much > easier to > install and remove. Yes, it's especially important to keep php.ini in the c:\php4 (or C:\php5 dir) now that we are drawing close to a new major release. > I have also planned on contacting server > vendors to help update the docs. The Sambar vendor added the right > instuctions as user comments on the sambar page for example. That's good. I hope the others are helpful :) --Wez.
RE: [PHP-DOC] restructuring the install section
I generally agree, but think that all the windows stuff should be grouped separately from the unixy platforms, as installation there is generally much simpler (stick the binaries in one place and tweak a couple of config files). + Unixy Systems + Apache + ... + Windows + Apache + IIS 6 (Win2k3) + IIS 5 (Win2k / WinXP) + ... I think it is also very important to stop telling people to put stuff in the windows systems folders, as this just causes problems. I can go through the win32 stuff once the restructuring is complete. --Wez. > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 18:14 > To: Nuno Lopes > Cc: PHPdoc > Subject: Re: [PHP-DOC] restructuring the install section > > > But there is a problem... You are moving the files from one > dir to another, > > but now the install part is organized by server and not by > operating system. > > The content will have to change in this move. > > And the ID's will be lost, too. > > for example, we have "install.apache2" that will be splited? to > > "install.win.apache2" and "install.nix.apache2" > > The hard part in the installation is that we need to have advice for > multiple operating systems and multiple webservers. This sometimes > causes problems. Since the document format is only capable of > having a > hierarhical TOC by nature, we need to decide on what will be > the primary > indexing method for us: OS or server. Currently this is not > really fixed. > > I would prefer something like the current method, mostly indexed by > webservers, and only having the OS specific instructions > separated when > needed. > > Goba >
[PHP-DOC] cvs: livedocs / livedoc_funcs.php xml_classes5.php
wez Tue May 25 11:24:47 2004 EDT
Modified files:
/livedocs livedoc_funcs.php xml_classes5.php
Log:
A couple of tweaks
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.1&r2=1.2&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.1 livedocs/livedoc_funcs.php:1.2
--- livedocs/livedoc_funcs.php:1.1 Tue May 25 07:33:48 2004
+++ livedocs/livedoc_funcs.php Tue May 25 11:24:46 2004
@@ -18,12 +18,15 @@
$nav = "";
/* Get the fileinfo for the reference */
- list($tr) = sqlite_array_query($idx, "SELECT title, filename, idents.fileid,
files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
+ $tr = sqlite_array_query($idx, "SELECT title, filename, idents.fileid,
files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
if (!$tr) {
- list($tr) = sqlite_array_query($fb_idx, "SELECT title, filename,
idents.fileid, files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
+ $tr = sqlite_array_query($fb_idx, "SELECT title, filename,
idents.fileid, files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
}
if ($tr) {
+ list($tr) = $tr;
list($title, $filename, $fileid, $dirid) = $tr;
+ } else {
+ $tr = array('?', '', -1, -1);
}
/* Get parent ID and child IDs */
http://cvs.php.net/diff.php/livedocs/xml_classes5.php?r1=1.1&r2=1.2&ty=u
Index: livedocs/xml_classes5.php
diff -u livedocs/xml_classes5.php:1.1 livedocs/xml_classes5.php:1.2
--- livedocs/xml_classes5.php:1.1 Tue May 25 07:33:48 2004
+++ livedocs/xml_classes5.php Tue May 25 11:24:46 2004
@@ -19,7 +19,7 @@
// | PHP 5 style |
// +--+
//
-// $Id: xml_classes5.php,v 1.1 2004/05/25 11:33:48 wez Exp $
+// $Id: xml_classes5.php,v 1.2 2004/05/25 15:24:46 wez Exp $
class Node { /* {{{ */
@@ -136,7 +136,7 @@
$this->tagname = $tagname;
$this->attributes = $attributes;
- $GLOBALS['__node_count']++;
+ @$GLOBALS['__node_count']++;
}
function set_parent($parent)
RE: [PHP-DOC] linuxtag this year
If you're still not seeing the usual traffic today, please drop a note to [EMAIL PROTECTED] and state which list doesn't appear to be working, as some changes have been made to the MX recently, and it may have been overlooked. --Wez. > -Original Message- > From: Nuno Lopes [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 14:56 > To: Gabor Hojtsy; Friedhelm Betz; PHPdoc; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] linuxtag this year > > > Cheers, > > > > For some reason, I don't receive the usual traffic from the PHP.net > > servers anymore. I don't know why... I have only spotted > this thread on > > the marc archives (and I am obviously unable to reply into the > > thread)... Last letters from the phpdoc list (and > php-mirrors stuff too) > > date back to May 23 afternoon. > > I'm having problems, too. I don't receive mails from the > notes mailling list > for 4 days Really strage!!
RE: [PHP-DOC] Re: cvs: livedocs / livedoc.php
Please try my latest commit; I fixed a few issues. --Wez. > -Original Message- > From: Mehdi Achour [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 11:51 > To: Ilia Alshanetsky > Cc: [EMAIL PROTECTED] > Subject: [PHP-DOC] Re: cvs: livedocs / livedoc.php > > Ilia Alshanetsky wrote: > > iliaa Mon May 24 16:59:28 2004 EDT > > > > Modified files: > > /livedocs livedoc.php > > Log: > > Optimizations: part #3. > > Did you coimmit everything ? Livedocs is broke now (every > link redirect to the > wonderfull search engine) > > Mehdi Achour >
[PHP-DOC] cvs: livedocs / configure.in livedoc.php livedoc_funcs.php mkindex.php pregenerate.php xml_classes5.php /themes/default html_format.php
[3];
} else {
$id = $ref;
}
$title = lookup_title($id);
if (!$title) {
$title = $id. ' [?]';
}
return "$title";
}
function do_contents($id, $level)
{
global $lang;
$ret = '';
if (($r = sqlite_array_query($GLOBALS['idx'], "SELECT id, docbook_id FROM toc
WHERE parent_id = ".$id, SQLITE_NUM))) {
foreach($r as $row) {
$ret .= "";
if (!($title = lookup_title($row[1]))) {
$ret .= $row[1]. ' [?]';
} else {
$ret .= "".$title."";
}
if (($level < 2 && strncmp($row[1], 'ref', 3)) || $level < 1)
{
$ret .= do_contents($row[0], $level + 1);
}
$ret .= "\n";
}
return "" . $ret . "\n";
}
return '';
}
function handle_include($node)
{
global $current_page;
$ref = $node->attributes['ref'];
$curr_lvl = sqlite_single_query($GLOBALS['idx'], "SELECT lvl from toc where
docbook_id='$current_page'");
list($row) = sqlite_array_query($GLOBALS['idx'], "SELECT idents.id, lvl from
ents left join files on ents.value = files.filename left join idents on files.fileid =
idents.fileid left join toc on ents.entid=toc.docbook_id where is_file=1 and
ents.entid='$ref' limit 1");
list($id, $lvl) = $row;
$filename = sqlite_single_query($GLOBALS['idx'], "SELECT value from ents where
entid='$ref' and is_file=1");
$path = PHPDOC . DIRECTORY_SEPARATOR . $filename;
if (!file_exists($path)) {
$path = PHPDOC . DIRECTORY_SEPARATOR . $GLOBALS['lang'] .
DIRECTORY_SEPARATOR . $filename;
}
if ($lvl > $curr_lvl) {
$fake->content = null;
$fake->attributes['linkend'] = $id;
$fake->tagname = 'xref';
return format_link($fake) . " [$ref, $id, $lvl vs $curr_lvl]";
}
$doc = load_xml_doc($path, true, null);
return "" . $doc->transform($GLOBALS['map']);
}
// Handle the case where a requested node id was not found
function handle_missing_index()
{
global $current_page, $lang;
header('Location: ' . WEBBASE . 'search.php?q=' . urlencode($current_page) .
'&l=' . $lang);
exit;
}
?>
http://cvs.php.net/co.php/livedocs/pregenerate.php?r=1.1&p=1
Index: livedocs/pregenerate.php
+++ livedocs/pregenerate.php
transform($map, $current_page);
$tgen = microtime(true) - $ts;
$gen_time += $tgen;
if ($NOTESDB) {
$tn = microtime(true);
fwrite(STDERR, "[notes]\t"); fflush(STDERR);
echo format_user_notes($current_page);
$gen_note = microtime(true) - $tn;
$note_time += $gen_note;
} else {
$gen_note = 0;
}
if (empty($file_revision)) {
$file_revision = 'unknown revision';
}
echo manual_page_footer();
$contents = ob_get_contents();
ob_clean();
$save_file = $lang . "/" . $current_page . ".html";
fwrite(STDERR, "\t$save_file "); fflush(STDERR);
$f = fopen($save_file, 'w');
fwrite($f, $contents);
fclose($f);
fwrite(STDERR, "\n"); fflush(STDERR);
$ts = microtime(true);
$nodes = $__node_count;
/* try to release as much memory as possible */
$page = null;
unset($page);
unset($nav);
unset($children);
unset($current_page_title);
unset($dirid);
unset($fileid);
unset($filename);
unset($title);
unset($file_revision);
unset($contents);
unset($f);
unset($save_file);
$tclean = microtime(true) - $ts;
$clean_time += $tclean;
fprintf(STDERR, "nav %.2fs, load %.2fs, gen %.2fs [note %.2fs], clean(%d) in
%.2fs\n\n",
$tnav, $tload,
$tgen, $gen_note, $nodes, $tclean);
if ($__node_count > 0) {
fwrite(STDERR, "nodes: $__node_count\n"); fflush(STDERR);
}
}
$elapsed = microtime(true) - $start_time;
fprintf(STDERR, "\nProcessed %d pages.\n\nOverall:%.2fs (%.2fs
each)\nGeneration: %.2fs(%.2fs each
RE: [PHP-DOC] Re: distribution of INI information in the manual
Please turn of read-reciepts when posting to the mailing lists. You can't possibly want to know when every single subscriber has read your email. > Hi all, > > I'm willing to host the livedocs site if everyone would like > me to host it. > > Regards > --jm
RE: [PHP-DOC] Re: distribution of INI information in the manual
If you come up with a concrete list of what you need to do, we should be able to sort something out. IIRC, the docs.php.net box is marked for phpdoc (but has some bandwidth problems?). --Wez. > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 24 May 2004 15:19 > To: Wez Furlong > Cc: 'Nuno Lopes'; 'Mehdi Achour'; 'PHPdoc'; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] Re: distribution of INI information in > the manual > > > I know you guys are overly prejudiced against systems@, but > why not run it on > > our own systems?? > > Our experience was that the guys at systems are already > overloaded with > work, and it would probably not be a good idea to put more > load on them. > There are some long awaiting stuff, which would need that new > machine. > The PDFs are not built for a long time now, and the so called 'new > machine' - which is probably building the HTML versions right > now - was > said to have enough resources to build the PDFs. There is a > good amount > of demand for them, and we need a strong machine to build them. > > Goba >
RE: [PHP-DOC] Re: distribution of INI information in the manual
I know you guys are overly prejudiced against systems@, but why not run it on our own systems?? --Wez. > > SF does not allow you to host some website which is not > closely related > > to the project you run on SF. We are not going to move the CVS to > > SF.net, so it is not justifyable to put any services there. > It does not > > fit into the terms of service AFAIK. > > Of course we aren't going to move CVS to SF.net servers, but... > We need a server to at least test livedocs. As belong to a > big open source > project... Let's wait for their answer! > > Nuno >
[PHP-DOC] cvs: livedocs /themes/default html_format.php
wez Mon May 24 08:43:25 2004 EDT Modified files: /livedocs/themes/defaulthtml_format.php Log: valign belongs on tr, not td http://cvs.php.net/diff.php/livedocs/themes/default/html_format.php?r1=1.9&r2=1.10&ty=u Index: livedocs/themes/default/html_format.php diff -u livedocs/themes/default/html_format.php:1.9 livedocs/themes/default/html_format.php:1.10 --- livedocs/themes/default/html_format.php:1.9 Sun May 23 04:58:01 2004 +++ livedocs/themes/default/html_format.php Mon May 24 08:43:25 2004 @@ -18,7 +18,7 @@ // | headers and footers for the HTML rendering | // +--+ // -// $Id: html_format.php,v 1.9 2004/05/23 08:58:01 wez Exp $ +// $Id: html_format.php,v 1.10 2004/05/24 12:43:25 wez Exp $ // in livedoc.php @@ -51,7 +51,7 @@ $filename $file_revision | generated: $date - + $nav @@ -160,7 +160,7 @@ $filename $file_revision | generated: $date - + $nav
RE: [PHP-DOC] Re: [patch] livedocs : Allowing entities in titles
> Your patch seems to be missing a $this->last_id somewhere, but I can't > test nothing now :( Should be fixed now; thanks :) > I also have a patch to exclude some unwanted dockbook ids, like > missing-stuff (see BUGS). I implmented it with a $banned_ids array > in the mk_XXX.php files et a if(in_array()) in mktoc.php. Do this > sounds good to you or should I change something ? Let's see the patch :)
[PHP-DOC] cvs: livedocs / mk_phpdoc.php
wez Mon May 24 08:19:39 2004 EDT
Modified files:
/livedocs mk_phpdoc.php
Log:
that should be "ignore files beginning with .#" not "ignore files named .#".
http://cvs.php.net/diff.php/livedocs/mk_phpdoc.php?r1=1.9&r2=1.10&ty=u
Index: livedocs/mk_phpdoc.php
diff -u livedocs/mk_phpdoc.php:1.9 livedocs/mk_phpdoc.php:1.10
--- livedocs/mk_phpdoc.php:1.9 Sun May 23 04:58:01 2004
+++ livedocs/mk_phpdoc.php Mon May 24 08:19:39 2004
@@ -18,7 +18,7 @@
// | Configuration file for phpdoc build |
// +--+
//
-// $Id: mk_phpdoc.php,v 1.9 2004/05/23 08:58:01 wez Exp $
+// $Id: mk_phpdoc.php,v 1.10 2004/05/24 12:19:39 wez Exp $
define('MK_VERSION', true);
define('MANUAL_TITLE', 'PHP Manual');
@@ -36,7 +36,7 @@
readdir($d); readdir($d);
while (($f = readdir($d))) {
- if (($f == 'functions.xml' && $section != 'language') || $f == 'CVS'
|| $f == '.cvsignore' || !strcmp('.#', $f)) {
+ if (($f == 'functions.xml' && $section != 'language') || $f == 'CVS'
|| $f == '.cvsignore' || !strncmp('.#', $f, 2)) {
continue;
}
switch (filetype($path . '/' . $f)) {
[PHP-DOC] cvs: livedocs / mkindex.php
wez Mon May 24 08:18:48 2004 EDT
Modified files:
/livedocs mkindex.php
Log:
Better id -> title handling.
http://cvs.php.net/diff.php/livedocs/mkindex.php?r1=1.33&r2=1.34&ty=u
Index: livedocs/mkindex.php
diff -u livedocs/mkindex.php:1.33 livedocs/mkindex.php:1.34
--- livedocs/mkindex.php:1.33 Sun May 23 04:58:01 2004
+++ livedocs/mkindex.phpMon May 24 08:18:48 2004
@@ -19,7 +19,7 @@
// | construct an index |
// +--+
//
-// $Id: mkindex.php,v 1.33 2004/05/23 08:58:01 wez Exp $
+// $Id: mkindex.php,v 1.34 2004/05/24 12:18:48 wez Exp $
/* just to be on the safe side */
@@ -59,6 +59,7 @@
var $last_id = false;
var $cdata = null;
var $data = '';
+ var $title_depth = -1;
function DocBookXMLFileParser($filename, $rel, $parser) {
$this->fileid = $GLOBALS['fileid'];
@@ -86,28 +87,31 @@
}
function start_elem($parser, $name, $attrs) {
+ static $titles = array('TITLE', 'REFNAME');
+
// if there is an ID attribute, record it
if (isset($attrs['ID'])) {
$this->last_id = $attrs['ID'];
}
+ if ($this->last_id !== false && in_array($name, $titles)) {
+ $this->title_depth = 1;
+ }
}
function end_elem($parser, $name) {
- if ($this->last_id !== false) {
+ if ($this->last_id !== false && $this->title_depth &&
--$this->title_depth == 0) {
echo "\tAdded ID {$this->last_id}\n";
- $this->data .= "INSERT INTO idents VALUES ('" .
strtolower($this->last_id) . "', {$this->fileid}, '" .
sqlite_escape_string(trim($this->cdata)) . "');";
+ $this->data .= "INSERT INTO idents VALUES ('" .
strtolower($this->last_id) . "', {$this->fileid}, '" .
sqlite_escape_string(str_replace('||amp||', '&', trim($this->cdata))) . "');";
$this->last_id = false;
+ $this->cdata = null;
}
}
function cdata($parser, $data) {
- if ($this->last_id !== false) {
- //small hack for '&'
- $data = str_replace('||amp||', '&', $data);
-
- $this->cdata = $data;
+ if ($this->title_depth) {
+ $this->cdata .= trim($data, "\r\n");
}
}
RE: [PHP-DOC] Linuxtag Karslruhe?
I will be at LinuxTag this year. > Is there any interest to take a docmeeting at Linuxtag in Karslruhe? > Last year we had a nice one and I guess some people of the doc-teams > are there. Should we meet again? > Infos about Linuxtag: http://www.linuxtag.org/2004/index.html
RE: [PHP-DOC] Re: [patch] livedocs : Allowing entities in titles
> Got it ? I can't be more clear than that :)
Perfect ;)
How about something like the attached patch instead, that should work with
your other case too (untested!).
> btw, I'm a missing something or is the query executed one
> more time upon
> failure line 180 ? Why ?
That looks like the only place where ->data gets executed to me.
--Wez.
Index: mkindex.php
===
RCS file: /repository/livedocs/mkindex.php,v
retrieving revision 1.33
diff -u -p -r1.33 mkindex.php
--- mkindex.php 23 May 2004 08:58:01 - 1.33
+++ mkindex.php 23 May 2004 12:50:12 -
@@ -59,6 +59,7 @@ class DocBookXMLFileParser {
var $last_id = false;
var $cdata = null;
var $data = '';
+ var $id_depth = -1;
function DocBookXMLFileParser($filename, $rel, $parser) {
$this->fileid = $GLOBALS['fileid'];
@@ -89,11 +90,12 @@ class DocBookXMLFileParser {
// if there is an ID attribute, record it
if (isset($attrs['ID'])) {
$this->last_id = $attrs['ID'];
+ $this->id_depth = 1;
}
}
function end_elem($parser, $name) {
- if ($this->last_id !== false) {
+ if ($this->last_id !== false && --$this->id_depth == 0) {
echo "\tAdded ID {$this->last_id}\n";
$this->data .= "INSERT INTO idents VALUES ('" .
strtolower($this->last_id) . "', {$this->fileid}, '" .
sqlite_escape_string(trim($this->cdata)) . "');";
@@ -107,7 +109,7 @@ class DocBookXMLFileParser {
//small hack for '&'
$data = str_replace('||amp||', '&', $data);
- $this->cdata = $data;
+ $this->cdata .= trim($data, "\r\n");
}
}
[PHP-DOC] cvs: phpdoc /en language-snippets.ent
wez Sun May 23 08:41:56 2004 EDT Modified files: /phpdoc/en language-snippets.ent Log: more detail on the ssl problem in IIS http://cvs.php.net/diff.php/phpdoc/en/language-snippets.ent?r1=1.88&r2=1.89&ty=u Index: phpdoc/en/language-snippets.ent diff -u phpdoc/en/language-snippets.ent:1.88 phpdoc/en/language-snippets.ent:1.89 --- phpdoc/en/language-snippets.ent:1.88Wed May 19 14:46:47 2004 +++ phpdoc/en/language-snippets.ent Sun May 23 08:41:56 2004 @@ -1,4 +1,4 @@ - + This extension is EXPERIMENTAL. The behaviour of this extension -- @@ -22,10 +22,16 @@ allow_url_fopen is enabled. '> -Some non-standard compliant -webservers, such as IIS, send data in a way that causes PHP to raise warnings. -When working with such servers you should lower your -error_reporting level not to include warnings.'> +When using SSL, Microsoft IISi +will violate the protocol by closing the connection without sending a +close_notify indicator. PHP will report this as "SSL: Fatal Protocol Error" +when you reach the end of the data. To workaround this, you should lower your +error_reporting level not to include warnings. +PHP 4.3.7 and higher can detect buggy IIS server software when you open +the stream using the https:// wrapper and will suppress the warning for you. +If you are using fsockopen to create an ssl:// socket, +you are responsible for detecting and suppressing the warning yourself. +'> This function will not work on remote files as the file to
RE: [PHP-DOC] livedocs PATCH
> > 2/ Although I want to solve the dom problem, I don't want
> to hard code dom
> > specifics into the guts of livedocs
> So how? How do you know if you to append 'dom-' to the id?
There should be a generic mechanism to name functions based on the extension
that they are in.
> > 3/ the version stuff is not phpdoc specific; it can happily
> live in the
> > default theme.
> No! PHPDOC is the only using the version stuff. With your
> modified patch, it
> works perfectly, because you are doing:
> if ($q && LATEST_VERSION == $q) {
This is correct.
> and I think the correct version would be:
> if (!$q || LATEST_VERSION == $q) {
>
> because If there is no version information on the DB, it is
> considered as
> 'CVS only', so it is only avaliable in latest version.
This is incorrect; read the comment in the source.
Not everything has version info (such as include/require) and this is showing
up incorrectly.
> Sorry, but I have tons of patches to livedocs... :) The
> issues adressed in
> the patch I sent are:
> * fixed a small problem with the message for outdated translations
> * fetch english entites if the translated aren't avaliable (in
> bind_entities)
> * a fix for references pages, like SPL or Tidy (make_function_link)
> * fix PCRE problem (handle_include)
> * hard-coded a fix for dom
> * small improvement for format_listing_hyperlink_function
> (don't link a
> function if $id== $current_page)
>
> I think thats all! ;-)
Can you please post one patch per issue? (I know it's a pain in the ass)
--Wez.
