Databases
StackOverflow2013
Postsdbo
POpyodbc does not throw on SQL Server error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpyodbc does not throw on SQL Server error
    primarykey
    data
    text
    <p>I am trying to use <code>pyodbc</code> (with Python 2.7) to call a stored procedure to insert records into a SQL Server 2012 table. I am passing a temporary table.</p> <p>I dumped out my sql and when executed through the SQL Server Management console, it generated the following Foreign Key error:</p> <pre><code>Msg 547, Level 16, State 0, Procedure spInsertBondTickerValues, Line 26 The INSERT statement conflicted with the FOREIGN KEY constraint "FK__BondTickerValue__756D6ECB". The conflict occurred in database "QuantDev", table "dbo.Tickers". The statement has been terminated. </code></pre> <p>However, <code>pyodbc</code> did not raise an exception. How would I test the resulting cursor or connection to know that a problem occurred, and how do I get the error message?</p> <p>Thank you very much.</p> <p><strong>EDIT</strong> Here is the full sql text:</p> <pre><code>DECLARE @rawTbl [dbo].TickerValueTableType INSERT INTO @rawTbl (Ticker, BBName, LastValue, ValueTime, SourceDescr) VALUES ('IBM', 'Equity', 179.230000, '2013-11-01 00:00:00.000000', 'Bloomberg'), ('SPX', 'Index', 1803.710000, '2013-12-10 00:00:00.000000', 'Bloomberg') EXEC [dbo].spInsertBondTickerValues @rawTbl </code></pre> <p><strong>EDIT 2</strong> Here is the relevant Python code:</p> <pre><code>def execSQLwithCommit(self, sql): cursor = self.conn.cursor() cursor.execute(sql) self.conn.commit() </code></pre> <p>where the connection has been previously made via</p> <pre><code>self.conn = pyodbc.connect(app = appName, driver = '{SQL Server Native client 11.0}', server = server, database = db, Trusted_Connection = 'yes') </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USgt6989b
    1. USgt6989b
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POpyodbc does not throw on SQL Server error
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POpyodbc does not throw on SQL Server error
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease update with the relevant python code where pyodbc.Cursor is instantiated and executed.
      singulars
      1. POpyodbc does not throw on SQL Server error
      1. USBryan
    2. CO@beargle Done. Thank you.
      singulars
      1. POpyodbc does not throw on SQL Server error
      1. USgt6989b
    3. COIt looks like your SQL script lacks any semicolons. I wonder if it gets parsed at all. SQL Server console might be smart enough to parse it, but is driver equally smart? I also suspect that the script has three distinct statements, each possibly requiring a separate `.execute` call.
      singulars
      1. POpyodbc does not throw on SQL Server error
      1. US9000
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload