so the simple solution is to disable the button after the call until the
results are returned
bastien> Date: Fri, 9 Nov 2007 15:02:31 -0500> From: [EMAIL PROTECTED]> To:
php-db@lists.php.net> Subject: [PHP-DB] Corrupted query results in memory.> > I
posted an issue to the mysql dev forums las
> This morning I figured out how to
> replicate the issue. Issue a double request for the mysql result set.
> Due to the "Ajaxy" nature of my web app it isn't the same as a double
> HTTPRequest of POST, as it is requesting a result set back from the
> database twice in a row before the response is
I posted an issue to the mysql dev forums last week with regards to an
issue we are encountering. The issue as we understood it last week was
simple...after some time (undetermined as of then) query results from
the web app (a PHP/MySQL/Javascript Ajax app.) would come back all
'wonky.' Upon issu
I've never worked with FileMaker before, but a quick Google
(http://www.filemaker.com/support/technologies/php.html) tells me you need
to get a copy of the FileMaker API for PHP, if you're not using Windows that
is. If you are using Windows you can use ODBC
(http://www.filemaker.com/help/15-Using%2
Happy Friday All!
We presently have an order form online (using php5) that feeds into a
FileMaker 9 database. What we are trying to do is:
If someone clicks on "cell phone" (checkbox), a new box of fields shows
under it requiring additional info that feeds into a new table in the
database (one o
There may be something useful here...
http://forge.mysql.com/
chris smith wrote:
> On Nov 9, 2007 1:18 AM, Colin Guthrie <[EMAIL PROTECTED]> wrote:
>
>> Lasitha Alawatta wrote:
>>
>>> There is a tool call "idera" (SQL diagnostic manager). Basically it is
>>> a performance monitoring and
Hiya
This seems to be one thing java has over php (perl etc) as it does know
about the warning and acts approperately. This should be an option to
ignore or not ignore warnings within php to prevent errorless truncation
of data.
Cheers
Andy
chris smith wrote:
On Nov 9, 2007 8:34 PM, Andrew
On Nov 9, 2007 8:34 PM, Andrew Blake <[EMAIL PROTECTED]> wrote:
> Hello
>
> It seems that the normal mysql_query doesn't error when an sql command
> forces the server to truncate the data. The mysql server executes the
> sql and provides a warning but it still executes the sql so allowing php
> to
Should i say badly written code to reproduce the problem
here is the code again with the errors
$db= mysql_connect($dbhost, $dbuser, $dbpass) or die ('Error
connecting to mysql');
$dbname = 'andy';
mysql_select_db($dbname);
$insertquery="insert into test values('012345678901234567891')";
$r
Hello
It seems that the normal mysql_query doesn't error when an sql command
forces the server to truncate the data. The mysql server executes the
sql and provides a warning but it still executes the sql so allowing php
to ignore the fact that there is a warning. You can run another sql
comma
10 matches
Mail list logo
