INSERTING AND DELETING ROWS IN THE SAME SESSION.

INSERTING AND DELETING ROWS IN THE SAME SESSION.

am 28.04.2003 20:37:52 von Andrew C F Dent

------=_NextPart_000_0005_01C30DBD.A8E16670
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

the application runs in cobol using ODBC and MYsql 3.23. When I insert =
and delete the same rows in the same transaction=20
I get an SQLCODE of zero but the rows are not deleted. I execute the =
same delete code without the insert and all is fine. Is this a feature? =
Is there a workaround ?=20

I am doing this because my backend application receives its data as a =
series of discrete transactions which it stores ( INSERTS) then when all =
the data has arrived it DELETES it from the temporary file and creates =
the final database records. I need to clean up the temporary inserts =
because they will block future transactions.


Thanks very much

Andrew Dent (UK)

------=_NextPart_000_0005_01C30DBD.A8E16670--

Re: INSERTING AND DELETING ROWS IN THE SAME SESSION.

am 29.04.2003 09:37:50 von Peter Zaitsev

On Mon, 2003-04-28 at 22:37, Andrew C F Dent wrote:
> the application runs in cobol using ODBC and MYsql 3.23. When I insert and delete the same rows in the same transaction
> I get an SQLCODE of zero but the rows are not deleted. I execute the same delete code without the insert and all is fine. Is this a feature? Is there a workaround ?
>
> I am doing this because my backend application receives its data as a series of discrete transactions which it stores ( INSERTS) then when all the data has arrived it DELETES it from the temporary file and creates the final database records. I need to clean up the temporary inserts because they will block future transactions.
>

Dear Andrew,

Unfortunately this does not looks like repeatable bug report.
Please specify exact MySQL and MyODBC versions are you using as well as
sequence of queries which leads to described behavior.

You can enable logging in ODBC to grab queries which are sent to the
server to make it easier to generate bug report.

--
MySQL 2003 Users Conf. -> http://www.mysql.com/events/uc2003/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org