execute_sql_string() will be suspend when there's an error in executing sqlString like primary key conflict

Open
#133 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, sql
Domain
databases

Research direction

Start at the execute_sql_string() entry point and reproduce the two-statement SQL example with sansTran=False, including the primary-key conflict in the second insert. Trace what happens after the error and the 'Executing : Execute SQL String' log; done means the call handles the conflict without suspending, with a regression test covering the behavior.

Written by the indexing model from the issue text.

Description

sqlString like below and sansTran=False:
insert into table1 values(xxx);insert into table2 values(xxx);
and there's an primary key conflict error when running 'insert into table2 values(xxx)'
then, execute_sql_string() will be suspend after log 'Executing : Execute SQL String | xxxxxx'

Dominant language
Python
Stars
179
Forks
178
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MarketSquare/Robotframework-Database-Library

All issues in MarketSquare/Robotframework-Database-Library

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.