I'm getting strange results that I think can be
explained by having an index that isn't set up right.
CREATE TABLE URL_POLICY (
url_id INTEGER NOT NULL,
policy_idINTEGER NOT NULL,
policy_order INTEGER NULL,
PRIMARY KEY (url_id, policy_id)
) TYPE=BDB;
INSERT INTO testtbl va
me in the right direction.
-Scott
------
Scott McCool
[EMAIL PROTECTED]
(571)633-5749
--
titute a waiver of any privilege or the
confidentiality of this message. If you have received this email in
error, please notify me immediately by reply and delete this message.
-Original Message-----
From: Scott McCool [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 13, 2001 1:01 PM
To: &#
I'm getting a very strange results all of the sudden when dealing with BLOBs
in a mysql 3.23.32 on a Solaris 7 (SPARC) machine (inserts/deletes handled
with the JDBC driver from http://mmmysql.sourceforge.net/)
If I do the following:
1) Create a BDB table with a blob column:
CREATE TABLE test4(
My guess is that this is what was happening. I'm not sure of any way to
confirm it though, how do I ensure that my select() is happening from a
different database page then the insert?
-Scott
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 16,
my select proceeds
fine.
Is there some reason the whole table seems to be locked from reads just
because someone has an uncommitted transaction?
The table type is BDB, it's running on Solaris 7/SPARC.
Thanks for any help you can offer!
-Scott
---------
Scott McCool
[
