MarketSquare / MarketSquare/Robotframework-Database-Library
execute_sql_string() will be suspend when there's an error in executing sqlString like primary key conflict
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 179
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
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'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100