I'm using MySQL 5.x InnoDB engine, transactional tables. I have a
conceptual design question. If I have a two columns 'a' and 'b', a is
the primary key, and b is a type double, in table 1 (T1) for which
column b will have many NULL values, do I leave it with an allow null
constraint on the column
al Message-
From: Dan Shirah [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 3:50 PM
To: Max Thayer
Cc: php-db@lists.php.net
Subject: Re: [PHP-DB] DB Design Concepts
Max,
I am assuming that since column b will only be populated 7% of the time
that it is not a value specific column (does not
**
Catchable fatal error: Object of class stdClass could not be
converted to string in on line
**
Catchable fatal error: Object of class stdClass could not be converted
to string in on line
Edit: I've added usage example and a clearer explanation of the code
snippet.
Catchable fatal error: Object of class stdClass could not be converted
to string in on line
*
I can only find the change log for PHP 5.2 identifying th
Thank you for responding to my requests for assistance.
Actually, the $dbh is the db handler object as stated in other PHP/PDO
examples $this->dbh = new PDO(...), that wasn't the area of issue,
however "the problem NOT being the problem..." was correct.
The issue with the code was subsequently on
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
Keeping in mind of course that the temporary table you create is only
accessible to the user who created it, and for the length of that
session connection. Once your script has finished executing and the
connection to the database is released, that temporary table no longer
exists. Net affect: ev
