Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 569439
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T13:17:43+00:00 2026-05-13T13:17:43+00:00

How do you handle errors in SQLAlchemy? I am relatively new to SQLAlchemy and

  • 0

How do you handle errors in SQLAlchemy? I am relatively new to SQLAlchemy and do not know yet.

Before I used SQLAlchemy, I would do things like

status = db.query("INSERT INTO users ...")
if (!status):
    raise Error, db.error

But now I am coding in SQLAlchemy and I do things like

user = User('Boda Cydo')
session.add(user)
session.commit()

No error checking whatsoever!

I do not like this coding style without error checking at all.

Please advice on how to check and handle errors in SQLAlchemy!

Sincerely, Boda Cydo.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T13:17:43+00:00Added an answer on May 13, 2026 at 1:17 pm

    Your example says:

    status = db.query("INSERT INTO users ...")
    if (!status):
        raise Error, db.error
    

    That seems to mean that you want to raise an exception if there’s some error on the query (with raise Error, db.error). However sqlalchemy already does that for you – so

    user = User('Boda Cydo')
    session.add(user)
    session.commit()
    

    Is just the same. The check-and-raise part is already inside SQLAlchemy.

    Here is a list of the errors sqlalchemy itself can raise, taken from help(sqlalchemy.exc) and help(sqlalchemy.orm.exc):

    • sqlalchemy.exc:
      • ArgumentError – Raised when an invalid or conflicting function argument is supplied.
        This error generally corresponds to construction time state errors.
      • CircularDependencyError – Raised by topological sorts when a circular dependency is detected
      • CompileError – Raised when an error occurs during SQL compilation
      • ConcurrentModificationError
      • DBAPIError – Raised when the execution of a database operation fails.
        If the error-raising operation occured in the execution of a SQL
        statement, that statement and its parameters will be available on
        the exception object in the statement and params attributes.
        The wrapped exception object is available in the orig attribute.
        Its type and properties are DB-API implementation specific.
      • DataError Wraps a DB-API DataError.
      • DatabaseError – Wraps a DB-API DatabaseError.
      • DisconnectionError – A disconnect is detected on a raw DB-API connection.
        be raised by a PoolListener so that the host pool forces a disconnect.
      • FlushError
      • IdentifierError – Raised when a schema name is beyond the max character limit
      • IntegrityError – Wraps a DB-API IntegrityError.
      • InterfaceError – Wraps a DB-API InterfaceError.
      • InternalError – Wraps a DB-API InternalError.
      • InvalidRequestError – SQLAlchemy was asked to do something it can’t do. This error generally corresponds to runtime state errors.
      • NoReferenceError – Raised by ForeignKey to indicate a reference cannot be resolved.
      • NoReferencedColumnError – Raised by ForeignKey when the referred Column cannot be located.
      • NoReferencedTableError – Raised by ForeignKey when the referred Table cannot be located.
      • NoSuchColumnError – A nonexistent column is requested from a RowProxy.
      • NoSuchTableError – Table does not exist or is not visible to a connection.
      • NotSupportedError – Wraps a DB-API NotSupportedError.
      • OperationalError – Wraps a DB-API OperationalError.
      • ProgrammingError – Wraps a DB-API ProgrammingError.
      • SADeprecationWarning – Issued once per usage of a deprecated API.
      • SAPendingDeprecationWarning – Issued once per usage of a deprecated API.
      • SAWarning – Issued at runtime.
      • SQLAlchemyError – Generic error class.
      • SQLError – Raised when the execution of a database operation fails.
      • TimeoutError – Raised when a connection pool times out on getting a connection.
      • UnboundExecutionError – SQL was attempted without a database connection to execute it on.
      • UnmappedColumnError
    • sqlalchemy.orm.exc:
      • ConcurrentModificationError – Rows have been modified outside of the unit of work.
      • FlushError – A invalid condition was detected during flush().
      • MultipleResultsFound – A single database result was required but more than one were found.
      • NoResultFound – A database result was required but none was found.
      • ObjectDeletedError – A refresh() operation failed to re-retrieve an object’s row.
      • UnmappedClassError – A mapping operation was requested for an unknown class.
      • UnmappedColumnError – Mapping operation was requested on an unknown column.
      • UnmappedError – TODO
      • UnmappedInstanceError – A mapping operation was requested for an unknown instance.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 357k
  • Answers 357k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer The other answers are correct. Here is some code you… May 14, 2026 at 9:40 am
  • Editorial Team
    Editorial Team added an answer you ruin the noConflict concept by reassigning the jquery to… May 14, 2026 at 9:40 am
  • Editorial Team
    Editorial Team added an answer If you get that particular error, you don't actually have… May 14, 2026 at 9:40 am

Related Questions

No related questions found

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.