[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-escape-string.xml
aidan Wed Aug 11 04:32:24 2004 EDT Modified files: /phpdoc/en/reference/mysql/functionsmysql-escape-string.xml Log: Noted the function is deprecated. http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-escape-string.xml?r1=1.9&r2=1.10&ty=u Index: phpdoc/en/reference/mysql/functions/mysql-escape-string.xml diff -u phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.9 phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.10 --- phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.9 Mon Jan 5 08:03:26 2004 +++ phpdoc/en/reference/mysql/functions/mysql-escape-string.xml Wed Aug 11 04:32:23 2004 @@ -1,5 +1,5 @@ - + @@ -54,6 +54,15 @@ + + + This function has been deprecated since PHP 4.3.0. + Do not use this function. Use mysql_real_escape_string + instead. + + + + See also mysql_real_escape_string, addslashes and the @@ -83,3 +92,17 @@ vim: et tw=78 syn=sgml vi: ts=1 sw=1 --> + +- mysql_escape_string calls MySQL's library function of the same name, which prepends slashes to the following characters: NUL (\x00), \n, \r, \, ', " and \x1a. + +- AddSlashes escapes NUL, ', " and \. + +$query = "SELECT * FROM adresses WHERE name='$name' AND private='N'"; + +mysql_query($query); +?> + +Without mysql_escape_string a user could set name to "' OR 1=1 OR ''='" + +effectively leading to the query: +SELECT * FROM adresses WHERE name='' OR 1=1 OR ''='' AND private='N' \ No newline at end of file
[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-escape-string.xml
aidan Wed Aug 11 04:40:28 2004 EDT Modified files: /phpdoc/en/reference/mysql/functionsmysql-escape-string.xml Log: Arrgh - Didn't read my diffs. Removed notes from bottom of file. http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-escape-string.xml?r1=1.10&r2=1.11&ty=u Index: phpdoc/en/reference/mysql/functions/mysql-escape-string.xml diff -u phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.10 phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.11 --- phpdoc/en/reference/mysql/functions/mysql-escape-string.xml:1.10Wed Aug 11 04:32:23 2004 +++ phpdoc/en/reference/mysql/functions/mysql-escape-string.xml Wed Aug 11 04:40:28 2004 @@ -1,5 +1,5 @@ - + @@ -91,18 +91,4 @@ vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 ---> - -- mysql_escape_string calls MySQL's library function of the same name, which prepends slashes to the following characters: NUL (\x00), \n, \r, \, ', " and \x1a. - -- AddSlashes escapes NUL, ', " and \. - -$query = "SELECT * FROM adresses WHERE name='$name' AND private='N'"; - -mysql_query($query); -?> - -Without mysql_escape_string a user could set name to "' OR 1=1 OR ''='" - -effectively leading to the query: -SELECT * FROM adresses WHERE name='' OR 1=1 OR ''='' AND private='N' \ No newline at end of file +--> \ No newline at end of file
Re: [PHP-DOC] System-dependent functions
Another example is touch(). It requires utime which I assume all OS's have although I don't know. And if not I assume PHP might essentially say "No utime huh? Let's use mtime/atime/ctime instead and define HAVE_UTIME as true." Again, I don't know this topic of utime so am only guessing here. AFAIR utime() is not available on Windows (?) Opinions of the proposed entity?: This function is system-dependent and may not be available in your copy of PHP. Use function_exists to be certain.'> This would confuse people IMHO. "System-dependant" might mean that it is OS specific (MacOS, Linux, Windows), or more fine graied, or ...? Goba
RE: [PHP-DOC] Proposal: CHANGELOG
On 10 August 2004 23:53, Philip Olson wrote: > > I'll work on some examples, this is going to be good. > > Here's an example where: > > * Two new sections: Parameter listing and CHANGELOG > * The parameter listing is a variablelist > * The CHANGELOG is a table > > http://livedocs.phpp.org/index.php?l=en&q=function.exif-thumbnail > > This looks pretty nice except the table has a title and we don't > need that so next we'll use an informal table. Also, the following > has a long description that pushes down the parameter listing but > it doesn't appear to be a major (or common) problem: > > http://livedocs.phpp.org/index.php?l=en&q=function.exif-read-data Oh, I like these! I have a few comments that I'd like to cast into the pool for discussion: (i) Personally, I'd like to see the Parameter Information and Change Log before the full description, so I'd go for something like: Definition(proto + *short* description of purpose -- the first para of each of these would suffice) Parameter List Change Log Return Values Description (the rest of the full description) However, YMMV! (ii) Parameter List: I'd like to see this kept as compact as possible, so I'd prefer to do without the vertical spacing between the parameter name and its description. (Also, if it were possible to merge the top and bottom dashed borders, that would be great!) However, I would like to see the type information repeated here, so I don't have to refer back to the proto if the associated description doesn't make it obvious to me (including an & if it's a by-reference parameter). In keeping with point (i), I'd also prefer these entries to be a minimal description of purpose, with amplification if necessary (such as the table for the "sections" parameter in exif_read_data()) in the long Description section. (iii) The Change Log table has a rather wide first column -- this may in part be due to the long title, which I think is excessive: "Version" would be quite sufficient IMO. (iv) Return Values: fine (but, as an aside, I'd question the wording of this particular example -- I think it should be a general rule to quote the principal return value first, with out-of-range possibilities afterwards, so: "Returns the embedded thumbnail, or FALSE if the image contains no thumbnail.") > Overall this seems like the way to go. Yay! Go for it! Cheers! Mike - Mike Ford, Electronic Information Services Adviser, Learning Support Services, Learning & Information Services, JG125, James Graham Building, Leeds Metropolitan University, Headingley Campus, LEEDS, LS6 3QS, United Kingdom Email: [EMAIL PROTECTED] Tel: +44 113 283 2600 extn 4730 Fax: +44 113 283 3211
Re: [PHP-DOC] libxml
moshe doron wrote: > you may didn't use the same chars due to your news client encoding > conversion. try to iconv chr(224); The same: >> It behaves the same in PHP 5.0.0 and PHP 4.3.8 on my box (Windows XP). >> Notice is issued and illegal characters are not translated. Jakub Vrana
RE: [PHP-DOC] Proposal: CHANGELOG
On Wed, 11 Aug 2004, Ford, Mike [LSS] wrote: > Oh, I like these! I have a few comments that I'd like to cast into > the pool for discussion: > > (i) Personally, I'd like to see the Parameter Information and Change > Log before the full description, so I'd go for something like: > > Definition(proto + *short* description of purpose -- the > first para of each of these would suffice) > Parameter List > Change Log > Return Values > Description (the rest of the full description) > > However, YMMV! I agree with this, but Changelog should be last. > (ii) Parameter List: I'd like to see this kept as compact as > possible, so I'd prefer to do without the vertical spacing > between the parameter name and its description. Yes, it's too large now, and please no dashed borders, just stick to the style that was already used on the page. > (iii) The Change Log table has a rather wide first column -- this > may in part be due to the long title, which I think is excessive: > "Version" would be quite sufficient IMO. Agreed. > > (iv) Return Values: fine (but, as an aside, I'd question the wording > of this particular example -- I think it should be a general rule > to quote the principal return value first, with out-of-range > possibilities afterwards, so: "Returns the embedded thumbnail, or > FALSE if the image contains no thumbnail.") yeah! Derick
[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-real-escape-string.xml
aidan Wed Aug 11 06:01:42 2004 EDT Modified files: /phpdoc/en/reference/mysql/functionsmysql-real-escape-string.xml Log: Whitespace changes http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml?r1=1.9&r2=1.10&ty=u Index: phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml diff -u phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.9 phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.10 --- phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.9Wed Jul 21 00:27:29 2004 +++ phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xmlWed Aug 11 06:01:42 2004 @@ -1,5 +1,5 @@ - + @@ -10,11 +10,11 @@ Description - - stringmysql_real_escape_string - stringunescaped_string - resourcelink_identifier - + + stringmysql_real_escape_string + stringunescaped_string + resourcelink_identifier + This function will escape special characters in the unescaped_string, taking into account the current
[PHP-DOC] cvs: phpdoc /en/reference/mysql/functions mysql-real-escape-string.xml
aidan Wed Aug 11 06:03:20 2004 EDT Modified files: /phpdoc/en/reference/mysql/functionsmysql-real-escape-string.xml Log: Removed initial example Added a massive example with information about sql injection attacks Added more information to the % and _ note Added a variablelist http://cvs.php.net/diff.php/phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml?r1=1.10&r2=1.11&ty=u Index: phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml diff -u phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.10 phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.11 --- phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xml:1.10 Wed Aug 11 06:01:42 2004 +++ phpdoc/en/reference/mysql/functions/mysql-real-escape-string.xmlWed Aug 11 06:03:20 2004 @@ -1,11 +1,12 @@ - + mysql_real_escape_string - Escapes special characters in a string for use in a SQL statement, taking into account the current charset of the connection. + Escapes special characters in a string for use in a SQL statement, + taking into account the current charset of the connection. @@ -16,46 +17,131 @@ resourcelink_identifier + + + unescaped_string + The string to escape + + + + link_identifier (optional) + The mysql connection resource + + + + This function will escape special characters in the unescaped_string, taking into account the current charset of the connection so that it is safe to place it in a - mysql_query. + mysql_query. If you wish to insert binary data + you must use this function. + + + mysql_real_escape_string calls MySQL's library function of the + same name, which prepends slashes to the following characters: + NULL, \x00, \n, + \r, \, ', + " and \x1a. + + + You must always (with few exceptions) use this function + to make your data safe before inserting. If you have + magic_quotes_gpc enabled, + you must first stripslashes your data. If you don't use + this, you'll leave yourself open to SQL Injection Attacks. Here's an example: - - - mysql_real_escape_string does not escape - % and _. - - - mysql_real_escape_string example + An example SQL Injection Attack - - The above example would produce the following output: - + +The query sent to MySQL: + + + This would allow anyone to log in without a valid password! Using + mysql_real_escape_string around each variable + prevents this. + + + + + + Our query is now safe no matter what the user submits! + + + + mysql_real_escape_string does not escape + % and _. These are wildcards in MySQL + if not bounded by quotes. + + See also - mysql_escape_string, mysql_client_encoding, addslashes, and the magic_quotes_gpc
Re: [PHP-DOC] Socket_Set_Option
> There should be a reference saying that socket_setop is a alias of http://us2.php.net/manual/en/function.socket-set-option.php . > -Anoynomus Hi, That page has a note about this: "This function used to be called socket_setopt() prior to PHP 4.3.0" And the sockets extension isn't a good choice. Just use the stream_xx funtions! Nuno
Re: [PHP-DOC] System-dependent functions
> I think this information should be individualized per function. Each > would mention the conditions that need to be met, and why it may not > be met. Having one entity for this will only scare the user and force > extra work on those who will have it available. I am guessing that > some of these conditions are always true (natively or artificially by > PHP) so that's something else to consider. Yep, I agree with you! There is an entity ¬e.no-windows; that serves this purpose. More might be created for other OS, but having just a message saying, your system may or may not have this functions doesn't help much! Nuno
[PHP-DOC] cvs: phpdoc /en/reference/errorfunc/functions error-reporting.xml
aidan Wed Aug 11 07:28:56 2004 EDT Modified files: /phpdoc/en/reference/errorfunc/functionserror-reporting.xml Log: Fixed typo http://cvs.php.net/diff.php/phpdoc/en/reference/errorfunc/functions/error-reporting.xml?r1=1.9&r2=1.10&ty=u Index: phpdoc/en/reference/errorfunc/functions/error-reporting.xml diff -u phpdoc/en/reference/errorfunc/functions/error-reporting.xml:1.9 phpdoc/en/reference/errorfunc/functions/error-reporting.xml:1.10 --- phpdoc/en/reference/errorfunc/functions/error-reporting.xml:1.9 Tue Feb 17 05:57:26 2004 +++ phpdoc/en/reference/errorfunc/functions/error-reporting.xml Wed Aug 11 07:28:56 2004 @@ -1,5 +1,5 @@ - + @@ -159,7 +159,7 @@ With PHP > 5.0.0 E_STRICT with value 2048 is available. E_ALL does NOT - include error levelE_STRICT. + include error level E_STRICT.
[PHP-DOC] #29614 [Opn]: Documentation error
ID: 29614 Updated by: [EMAIL PROTECTED] Reported By: nramsbottom at hotmail dot com Status: Open -Bug Type:Website problem +Bug Type:Documentation problem PHP Version: Irrelevant New Comment: PHP Manual problem, so classify as such Previous Comments: [2004-08-11 14:14:13] nramsbottom at hotmail dot com Description: There appears to be an error in the PHP manual for PHP5 class member visibility located at: http://www.php.net/manual/en/language.oop5.visibility.php >Protected limits access access to only classes inherited. Protected limits visiblity only to the class that defines the item. Also... > Class members must be defined with public, private, or private. -- Edit this bug report at http://bugs.php.net/?id=29614&edit=1
[PHP-DOC] #29614 [Opn->Csd]: Documentation error
ID: 29614 Updated by: [EMAIL PROTECTED] Reported By: nramsbottom at hotmail dot com -Status: Open +Status: Closed Bug Type:Documentation problem PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. These typos have already been fixed by tularis and nlopess (respectively), and we're just waiting on a manual rebuild for them to be viewable. Previous Comments: [2004-08-11 14:46:43] [EMAIL PROTECTED] PHP Manual problem, so classify as such [2004-08-11 14:14:13] nramsbottom at hotmail dot com Description: There appears to be an error in the PHP manual for PHP5 class member visibility located at: http://www.php.net/manual/en/language.oop5.visibility.php >Protected limits access access to only classes inherited. Protected limits visiblity only to the class that defines the item. Also... > Class members must be defined with public, private, or private. -- Edit this bug report at http://bugs.php.net/?id=29614&edit=1
[PHP-DOC] [Fwd: Re: updating the install files]
Can someone please fix this. Thanks, Goba --- Begin Message --- Goba I just spotted Andi's commits of the new installation instructions. Good work! Can I suggest a slight improvement to the section on the Windows installer versions (this reflects some changes made to the installer over the last year): This paragraph relating to the installer version: The installation wizard gathers enough information to set up the php.ini file, and configure certain web servers to use PHP. With IIS or PWS on a NT Workstation, a list of all the nodes on the server with script map settings is displayed, and you can choose those nodes to which you wish to add the PHP script mappings. One of the web servers the PHP installer does not configure for is Apache, so you'll need to configure it manually. would now be more accurate if it was worded thus: The installation wizard gathers enough information to set up the php.ini file, and configure certain web servers to use PHP. One of the web servers the PHP installer does not configure for is Apache, so you'll need to configure it manually. Cheers -- Phil Driscoll --- End Message ---
Re: [PHP-DOC] System-dependent functions
> > Another example is touch(). It requires utime which I assume all > > OS's have although I don't know. And if not I assume PHP might > > essentially say "No utime huh? Let's use mtime/atime/ctime instead > > and define HAVE_UTIME as true." Again, I don't know this topic of > > utime so am only guessing here. > > AFAIR utime() is not available on Windows (?) Maybe not but PHP says it is as I'm guessing it makes it so. My comment above was based off this because the sources require HAVE_UTIME for touch() to exist and touch() exists on Windows. On a related note (although this is getting a little offtopic :) the 4.2.3 changelog has this: Fixed a bug that prevented touch() from working on various platforms. (Steph) Not sure what that means exactly though. Another similar example is sendmail. There is a HAVE_SENDMAIL as well that's defined as true for Windows, and in that case win32/sendmail.c is used. So telling people they need sendmail would be confusing as it's simply not true. That and the fact that other OS's may use alternatives like qmail and postfix. But I'm not trying to be informative on the topics of utime/sendmail (I can't), just trying to make a point ;) > >>Opinions of the proposed entity?: > >> > >>This function is system-dependent > >>and may not be available in your copy of PHP. Use > >>function_exists to be certain.'> > > This would confuse people IMHO. "System-dependant" might mean that it is > OS specific (MacOS, Linux, Windows), or more fine graied, or ...? Agreed. Usually it's Windows versus the rest of the world but many times it's because of a required library, a library that we should mention as long as a "in-house alternative" does not exist. Or maybe we could even mention that but most likely not. Regards, Philip
RE: [PHP-DOC] Proposal: CHANGELOG
> > Oh, I like these! I have a few comments that I'd like to cast into > > the pool for discussion: > > > > (i) Personally, I'd like to see the Parameter Information and Change > > Log before the full description, so I'd go for something like: > > > > Definition(proto + *short* description of purpose -- the > > first para of each of these would suffice) > > Parameter List > > Change Log > > Return Values > > Description (the rest of the full description) > > > > However, YMMV! > > I agree with this, but Changelog should be last. I thought about this but here's why I went with one description. First, the short definition (purpose) is already in the refpurpose of the function. Also, writing a summary for each would be a bit too difficult. As far as using just the first para, I think it'd be confusing having it so far apart from the rest of the description as they are often tied together. And something to keep in mind is long descriptions are rare. I agree return values should go after the parameter list. So here's my thoughts on the matter: Description (full) Parameter List Return Values Changelog Examples See Also The changelog has important information, enough so that it should go before the examples. I believe the only part that needs further discussion and thought is the Description. > > (ii) Parameter List: I'd like to see this kept as compact as > > possible, so I'd prefer to do without the vertical spacing > > between the parameter name and its description. > > Yes, it's too large now, and please no dashed borders, just stick to the > style that was already used on the page. I'm not concerned with the look of livedocs right now and it uses the default livedoc style sheets (nothing was altered), just a simple . > > (iii) The Change Log table has a rather wide first column -- this > > may in part be due to the long title, which I think is excessive: > > "Version" would be quite sufficient IMO. > > Agreed. Sounds good. > > > > (iv) Return Values: fine (but, as an aside, I'd question the wording > > of this particular example -- I think it should be a general rule > > to quote the principal return value first, with out-of-range > > possibilities afterwards, so: "Returns the embedded thumbnail, or > > FALSE if the image contains no thumbnail.") > > yeah! This is how functions are done currently, except a few, like this one ;) This rule will be added to the HOWTO although IIRC it's listed somewhere. Regards, Philip.
Re: [PHP-DOC] Proposal: CHANGELOG
I thought about this but here's why I went with one description. First, the short definition (purpose) is already in the refpurpose of the function. Also, writing a summary for each would be a bit too difficult. As far as using just the first para, I think it'd be confusing having it so far apart from the rest of the description as they are often tied together. And something to keep in mind is long descriptions are rare. I agree return values should go after the parameter list. So here's my thoughts on the matter: Description (full) Parameter List Return Values Changelog Examples See Also The changelog has important information, enough so that it should go before the examples. I believe the only part that needs further discussion and thought is the Description. Chagelog affects parameters, return values, and other types of behaviour, so it should be after the description of these IMHO. I am fine with Philip's above suggestion. Goba
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions explode.xml
nlopess Wed Aug 11 12:19:15 2004 EDT Modified files: /phpdoc/en/reference/strings/functions explode.xml Log: document new PHP 5.1 feature: negative limit http://cvs.php.net/diff.php/phpdoc/en/reference/strings/functions/explode.xml?r1=1.7&r2=1.8&ty=u Index: phpdoc/en/reference/strings/functions/explode.xml diff -u phpdoc/en/reference/strings/functions/explode.xml:1.7 phpdoc/en/reference/strings/functions/explode.xml:1.8 --- phpdoc/en/reference/strings/functions/explode.xml:1.7 Thu Jul 22 18:51:12 2004 +++ phpdoc/en/reference/strings/functions/explode.xml Wed Aug 11 12:19:15 2004 @@ -1,5 +1,5 @@ - + @@ -31,6 +31,11 @@ return an array containing string. + If the limit parameter is negative, all components + except the last limit are returned. This feature + was added in PHP 5.1.0. + + Although implode can, for historical reasons, accept its parameters in either order, explode cannot. You must ensure that the @@ -64,6 +69,42 @@ ?> ]]> + + + + + limit parameter examples + + + + + The above example will output: + + + +
Re: [PHP-DOC] Proposal: CHANGELOG
Gabor Hojtsy wrote: I thought about this but here's why I went with one description. First, the short definition (purpose) is already in the refpurpose of the function. Also, writing a summary for each would be a bit too difficult. As far as using just the first para, I think it'd be confusing having it so far apart from the rest of the description as they are often tied together. And something to keep in mind is long descriptions are rare. I agree return values should go after the parameter list. So here's my thoughts on the matter: Description (full) Parameter List Return Values Changelog Examples See Also The changelog has important information, enough so that it should go before the examples. I believe the only part that needs further discussion and thought is the Description. Chagelog affects parameters, return values, and other types of behaviour, so it should be after the description of these IMHO. I am fine with Philip's above suggestion. Fine with me too. Mehdi
[PHP-DOC] cvs: phpdoc /en/reference/pcre pattern.syntax.xml
daveWed Aug 11 16:15:30 2004 EDT
Modified files:
/phpdoc/en/reference/pcre pattern.syntax.xml
Log:
- Add < and fix assertion. Fixes #29621.
http://cvs.php.net/diff.php/phpdoc/en/reference/pcre/pattern.syntax.xml?r1=1.3&r2=1.4&ty=u
Index: phpdoc/en/reference/pcre/pattern.syntax.xml
diff -u phpdoc/en/reference/pcre/pattern.syntax.xml:1.3
phpdoc/en/reference/pcre/pattern.syntax.xml:1.4
--- phpdoc/en/reference/pcre/pattern.syntax.xml:1.3 Sat Aug 7 11:07:57 2004
+++ phpdoc/en/reference/pcre/pattern.syntax.xml Wed Aug 11 16:15:29 2004
@@ -1,5 +1,5 @@
-
+
@@ -1456,7 +1456,7 @@
matches an occurrence of "baz" that is preceded by "bar"
which in turn is not preceded by "foo", while
- (?<=\d{3}(?!999)...)foo
+ (?<=\d{3}...(?
[PHP-DOC] cvs: phpdoc /en/appendices resources.xml /en/install/windows apache1.xml
daveWed Aug 11 16:28:39 2004 EDT Modified files: /phpdoc/en/appendices resources.xml /phpdoc/en/install/windows apache1.xml Log: - Microsft => Microsoft. http://cvs.php.net/diff.php/phpdoc/en/appendices/resources.xml?r1=1.31&r2=1.32&ty=u Index: phpdoc/en/appendices/resources.xml diff -u phpdoc/en/appendices/resources.xml:1.31 phpdoc/en/appendices/resources.xml:1.32 --- phpdoc/en/appendices/resources.xml:1.31 Tue Aug 3 16:59:42 2004 +++ phpdoc/en/appendices/resources.xml Wed Aug 11 16:28:39 2004 @@ -1,5 +1,5 @@ - + List of Resource Types @@ -1279,7 +1279,7 @@ mssql_close -Link to Microsft SQL Server database +Link to Microsoft SQL Server database mssql link persistent @@ -1293,7 +1293,7 @@ None -Persistent link to Microsft SQL Server +Persistent link to Microsoft SQL Server mssql result @@ -1317,7 +1317,7 @@ mssql_free_result -Microsft SQL Server result +Microsoft SQL Server result mysql link http://cvs.php.net/diff.php/phpdoc/en/install/windows/apache1.xml?r1=1.9&r2=1.10&ty=u Index: phpdoc/en/install/windows/apache1.xml diff -u phpdoc/en/install/windows/apache1.xml:1.9 phpdoc/en/install/windows/apache1.xml:1.10 --- phpdoc/en/install/windows/apache1.xml:1.9 Sat Aug 7 15:18:24 2004 +++ phpdoc/en/install/windows/apache1.xml Wed Aug 11 16:28:39 2004 @@ -1,7 +1,7 @@ - + -Apache 1.3.x on Microsft Windows +Apache 1.3.x on Microsoft Windows This section contains notes and hints specific to Apache 1.3.x installs of PHP on Microsoft Windows systems. We also
[PHP-DOC] #29601 [Opn]: sqlite_query() return resource handles for non-row returning sql
ID: 29601 Updated by: [EMAIL PROTECTED] Reported By: Jared dot Williams1 at ntlworld dot com Status: Open -Bug Type: SQLite related +Bug Type: Documentation problem Operating System: Windows 2000/IIS PHP Version: 5CVS-2004-08-10 (dev) New Comment: Documentation problem. Previous Comments: [2004-08-10 16:06:50] Jared dot Williams1 at ntlworld dot com Description: It appears sqlite_query() and sqlite_unbuffered_query() differ from the documentation >From http://uk.php.net/manual/en/function.sqlite-query.php For queries that return rows, this function will return a result handle which can then be used with functions such as sqlite_fetch_array() and sqlite_seek(). For other kinds of queries, this function will return a boolean result; TRUE for success or FALSE for failure. Seems a handle is returned irrespective of the type of query. Reproduce code: --- 10')); @sqlite_close($cnn); } ?> Expected result: bool(true) Actual result: -- resource(2) of type (sqlite result) -- Edit this bug report at http://bugs.php.net/?id=29601&edit=1
[PHP-DOC] Not an active author?
I'm resisting the urge to move my name from "Inactive authors" to the main page. More curious what criteria was used to determine who's active and who isn't. -Sara
[PHP-DOC] cvs: phpdoc /en/reference/regex/functions spliti.xml
damsWed Aug 11 21:17:37 2004 EDT Modified files: /phpdoc/en/reference/regex/functionsspliti.xml Log: Fixing preg_spliti http://cvs.php.net/diff.php/phpdoc/en/reference/regex/functions/spliti.xml?r1=1.3&r2=1.4&ty=u Index: phpdoc/en/reference/regex/functions/spliti.xml diff -u phpdoc/en/reference/regex/functions/spliti.xml:1.3 phpdoc/en/reference/regex/functions/spliti.xml:1.4 --- phpdoc/en/reference/regex/functions/spliti.xml:1.3 Fri Jun 20 17:31:15 2003 +++ phpdoc/en/reference/regex/functions/spliti.xml Wed Aug 11 21:17:36 2004 @@ -1,5 +1,5 @@ - + @@ -22,7 +22,7 @@ characters. - See also preg_spliti, split, + See also preg_split, split, explode, and implode.
[PHP-DOC] cvs: phpdoc /scripts check-valid-function.php
daveWed Aug 11 23:11:43 2004 EDT
Added files:
/phpdoc/scripts check-valid-function.php
Log:
- Add a script that checks for non-functions inbetween tags.
Using this would have caught bug #29622 sooner.
http://cvs.php.net/co.php/phpdoc/scripts/check-valid-function.php?r=1.1&p=1
Index: phpdoc/scripts/check-valid-function.php
+++ phpdoc/scripts/check-valid-function.php
http://www.php.net/license/3_0.txt. |
| If you did not receive a copy of the PHP license and are unable to |
| obtain it through the world-wide-web, please send a note to |
| [EMAIL PROTECTED] so we can mail you a copy immediately. |
+--+
| Authors:Dave Barr <[EMAIL PROTECTED]> |
+--+
| Description: This file parses the manual and outputs all erroneous |
| tag usage. |
+--+
*/
/* path to phpdoc CVS checkout. if this file is in the scripts/ directory
* then the value below will be correct!
*/
$phpdoc = '../';
/* english! */
$lang = 'en';
/* initialize array and declare some language constructs */
$funcs = array( 'include' => true,
'include_once' => true,
'require' => true,
'require_once' => true,
'return' => true,
);
$total = 0;
/* recursive glob() with a callback function */
function globbetyglob($globber, $userfunc)
{
foreach (glob("$globber/*") as $file) {
if (is_dir($file)) {
globbetyglob($file, $userfunc);
}
else {
call_user_func($userfunc, $file);
}
}
}
/* make a function list from files in the functions/ directories */
function make_func_list($file)
{
global $funcs;
if (fnmatch("*/reference/*/functions/*.xml", $file)) {
$func = strtolower(str_replace(array('-', '.'), '_', substr(basename($file),
0, -4)));
$funcs[$func] = true;
}
}
/* find all tags and report invalid functions */
function parse_file($file)
{
global $funcs, $phpdoc, $lang, $total;
/* ignore old functions directory */
if (fnmatch("$phpdoc/$lang/functions/*", $file))
return;
$f = file_get_contents($file);
if ($f != '') {
if (preg_match_all('|(.*?)|s', $f, $m)
&& is_array($m)
&& is_array($m[1]))
{
foreach ($m[1] as $func) {
$func = strtolower(str_replace(array('::', '->'), '_', trim($func)));
if ($funcs[$func] !== true) {
$total++;
$fileout = substr($file, strlen($phpdoc) + 1);
printf("%-60.60s $func\n", $fileout);
}
}
}
}
}
echo "Building a list of functions...\n";
globbetyglob("$phpdoc/$lang", 'make_func_list');
echo 'List complete. ' . count($funcs) . " functions.\n";
echo "Checking the manual for tags that contain invalid functions...\n";
globbetyglob("$phpdoc/$lang", 'parse_file');
echo "Found $total occurences.\n";
?>
[PHP-DOC] #29367 [Csd->Opn]: mysqli_stmt_init() typo
ID: 29367 User updated by: jsgoupil at lookstrike dot com Reported By: jsgoupil at lookstrike dot com -Status: Closed +Status: Open Bug Type:Documentation problem PHP Version: Irrelevant New Comment: You know that there is always the same "bug" in other languages... Previous Comments: [2004-07-24 21:35:50] [EMAIL PROTECTED] What's funny is I fixed this about an hour ago :) It'll show up when the manual is next built, here's the diff: http://cvs.php.net/diff.php/phpdoc/en/reference/mysqli/functions/mysqli-stmt-init.xml?r1=1.3&r2=1.4 Thanks for the report! [2004-07-24 21:29:33] jsgoupil at lookstrike dot com Description: In the page http://ca3.php.net/manual/fr/function.mysqli-stmt-init.php We can see mysqli_stmt-init and lower in the page, we can see mysqli_stmt_init. (I think it is in all languages and also in the list of the functions on the left, and also in the last list of function on http://ca3.php.net/manual/en/ref.mysqli.php) We can also see on http://ca3.php.net/manual/en/ref.mysqli.php "stmt_initInitializes a statement for use with mysqli_stmt_prepare" (There is no dash to seperate the function and explanation) English Only Expected result: Supposed to be mysqli_stmt_init() ? -- Edit this bug report at http://bugs.php.net/?id=29367&edit=1
