Ok, bug closed now with PHP 4.0.4 pl1 mysql 3.22.xxx
and apache 1.3.12.

No more problems were founded for 1 week now with
mysql commands.

NP.

--- Bug Database <[EMAIL PROTECTED]> a écrit : >
ID: 6722
> Updated by: cynic
> Reported By: [EMAIL PROTECTED]
> Old-Status: Open
> Status: Feedback
> Bug Type: MySQL related
> Assigned To: 
> Comments:
> 
> have you experienced this error with newer versions
> of PHP?
> 
> Previous Comments:
>
---------------------------------------------------------------------------
> 
> [2000-09-13 18:38:09] [EMAIL PROTECTED]
> we're using a Apache 1.3.12 Server + PHP 4.02 +
> MySQL on a Sun Ultra 250  - 256Mo RAM Patched
> 106541-11
> 
> we have the same message while
> connecting/select_db/query/fetch_row
> 
> "Not a valid MYSQL result resource ..."
> 
> mysql_error($connection_id) gives us : "Lost
> connection to MySQL server during query"
> 
> we consult the bug reporting list and :
> - when we make a gettype($connection_id) ->
> "resource"
> 
> - we tried to remove the second parameter
> ($connection_id) in query -> nothing came
> 
> In fact, the pb appears sometimes at every request
> and sometimes do not appears for 4/5 same requests.
> It's very unregular !
> 
> 
> 
> Source : 
> 
> <HTML>
> <?
> $cx_si = mysql_connect("localhost","root","toto");
> mysql_select_db("si",$cx_si);
> $sql = "select * from USERS;";
> $st_si = mysql_query($sql);
> echo("after : " . mysql_error($cx_si) . "<BR>");
> echo("after query 2: " . gettype($cx_si) . "<BR>");
> echo("st_si: " . gettype($st_si) . "<BR>");
> echo("st_si: " . $st_si . "<BR>");
> $temp = mysql_fetch_row($st_si);
> ?>
> </HTML>
> 
> 
> we made many recompilations with differents releases
> of apache(from 1.3.9 to 1.3.12), php with 4.01pl2
> and 4.0.2
> 
> the database is correctly
> installed/configured/database accessible from the
> external
> 
> the table's got an unique index and contains two
> records
> 
> we tried to make a select * from table where 1=1 and
> 2=2 ...
> to make the select bigger -> nothing came
> 
> 
> 
> PHP Configuration : we followed strictly the
> configuration operations show in the page
> installation for uniw static mode on www.php.net
> We are now testing the dynamic mode ...
> 
> 
> Please could you tell us if you have already noticed
> this problem before with such a configuration ??
> 
> Thanks by advance.
> 
> Nicolas.
> 
> 
> 
> 
> PHP.INI:
> 
> [PHP]
> 
> ;;;;;;;;;;;;;;;;;;;
> ; About this file ;
> ;;;;;;;;;;;;;;;;;;;
> ; This file controls many aspects of PHP's behavior.
>  In order for PHP to
> ; read it, it must be named 'php.ini'.  PHP looks
> for it in the current
> ; working directory, in the path designated by the
> environment variable
> ; PHPRC, and in the path that was defined in compile
> time (in that order).
> ; Under Windows, the compile-time path is the
> Windows directory.  The
> ; path in which the php.ini file is looked for can
> be overriden using
> ; the -c argument in command line mode.
> ;
> ; The syntax of the file is extremely simple. 
> Whitespace and Lines
> ; beginning with a semicolon are silently ignored
> (as you probably guessed).
> ; Section headers (e.g. [Foo]) are also silently
> ignored, even though
> ; they might mean something in the future.
> ;
> ; Directives are specified using the following
> syntax:
> ; directive = value
> ; Directive names are *case sensitive* - foo=bar is
> different from FOO=bar.
> ;
> ; The value can be a string, a number, a PHP
> constant (e.g. E_ALL or M_PI), one
> ; of the INI constants (On, Off, True, False, Yes,
> No and None) or an expression
> ; (e.g. E_ALL & ~E_NOTICE), or a quoted string
> ("foo").
> ;
> ; Expressions in the INI file are limited to bitwise
> operators and parentheses:
> ; |                           bitwise OR
> ; &                           bitwise AND
> ; ~                           bitwise NOT
> ; !                           boolean NOT
> ;
> ; Boolean flags can be turned on using the values 1,
> On, True or Yes.
> ; They can be turned off using the values 0, Off,
> False or No.
> ;
> ; An empty string can be denoted by simply not
> writing anything after the equal
> ; sign, or by using the None keyword:
> ;
> ;   foo =                     ; sets foo to an empty string
> ;     foo = none              ; sets foo to an empty string
> ;     foo = "none"    ; sets foo to the string 'none'
> ;
> ; If you use constants in your value, and these
> constants belong to a dynamically
> ; loaded extension (either a PHP extension or a Zend
> extension), you may only
> ; use these constants *after* the line that loads
> the extension.
> ;
> ; All the values in the php.ini-dist file correspond
> to the builtin
> ; defaults (that is, if no php.ini is used, or if
> you delete these lines,
> ; the builtin defaults will be identical).
> 
> 
> ;;;;;;;;;;;;;;;;;;;;
> ; Language Options ;
> ;;;;;;;;;;;;;;;;;;;;
> 
> engine                        =       On      ; Enable the PHP scripting language
> engine under Apache
> short_open_tag        =       On      ; allow the <? tag.  otherwise,
> only <?php and <script> tags are recognized.
> asp_tags              =       Off ; allow ASP-style <% %> tags
> precision             =       14      ; number of significant digits
> displayed in floating point numbers
> y2k_compliance        =       Off     ; whether to be year 2000
> compliant (will cause problems with non y2k
> compliant browsers)
> output_buffering      = Off   ; Output buffering allows you
> to send header lines (including cookies)
>                                                       ; even after you send body 
>content, in the
> price of slowing PHP's
>                                                       ; output layer a bit.
>                                                       ; You can enable output 
>buffering by in
> runtime by calling the output
>                                                       ; buffering functions, or 
>enable output
> buffering for all files
>                                                       ; by setting this directive to 
>On.
> implicit_flush                = Off   ; Implicit flush tells PHP to
> tell the output layer to flush itself
>                                                       ; automatically after every 
>output block. 
> This is equivalent to
>                                                       ; calling the PHP function 
>flush() after each
> and every call to print()
>                                                       ; or echo() and each and every 
>HTML block.
>                                                       ; Turning this option on has 
>serious
> performance implications, and
>                                                       ; is generally recommended for 
>debugging
> purposes 
=== message truncated ===


=====
Nicolas PERRIN
Consultant ODNS
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Tél: (33) 06.20.31.50.36 / (33) 01.64.80.90.90

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to