Bug #6294 Updated: Strange behaviour when using DB2
| From: | sander@php.net | Date: | Tue, 18 Dec 2001 12:14:09 +0000 |
| Subject: | Bug #6294 Updated: Strange behaviour when using DB2 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-74237@lists.php.net to get a copy of this message | ||
ID: 6294
Updated by: sander
Reported By: ltning@anduin.net
Old Status: Feedback
Status: Closed
Bug Type: ODBC related
Operating System: RedHat Linux 6.2
PHP Version: 4.0.1pl2
New Comment:
No feedback. Closing.
Previous Comments:
------------------------------------------------------------------------
[2001-11-27 05:34:54] sander@php.net
Does this problem still occur with 4.0.6, the latest RC
(http://download.php.net/~zeev/php-4.1.0RC3.tar.gz) or the latest CVS?
------------------------------------------------------------------------
[2001-04-10 13:30:32] ltning@anduin.net
No, since the GENERATE_UNIQUE() function, which relies on a FOR BIT DATA field still won't
work. It seems to be the FOR BIT DATA variants of the CHAR fields that PHP has problems with, and
even though I haven't bumped into more situations where I need this, It sure will happen at
some point - I can imagine I'll encounter the problem when we next month start to store product
pictures in the database. A such field type would be convenient to use, as an alternative to xLOB
fields..
------------------------------------------------------------------------
[2001-04-10 09:28:41] kalowsky@php.net
Please use the Bug system to respond to bugs.
User Reports:
No, since the GENERATE_UNIQUE() function, which relies on a FOR BIT DATA field still won't
work. It seems to be the FOR BIT DATA variants of the CHAR fields that PHP has problems with, and
even though I haven't bumped into more situations where I need this, It sure will happen at
some point - I can imagine I'll encounter the problem when we next month start to store product
pictures in the database. A such field type would be convenient to use, as an alternative to xLOB
fields..
Best regards,
Eirik Overby
------------------------------------------------------------------------
[2001-04-09 11:11:12] kalowsky@php.net
Judging by your second comment, would you consider this bug closed?
------------------------------------------------------------------------
[2000-08-22 11:26:07] ltning@anduin.net
I have been able to narrow the problem down to the useage of the "FOR BIT DATA" modifier
to the CHAR type.
To use the GENERATE_UNIQUE() function in DB2, one must have a CHAR(13) FOR BIT DATA field. When
working with a table with such a field, PHP seems to choke and do many strange things.. Now that I
redesigned the database into just using plain CHAR(13) fields (planning to use uniqid()), everything
seems to work a lot better.
-Eirik
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=6294
Edit this bug report at http://bugs.php.net/?id=6294&edit=1