Yahoo Poland Wyszukiwanie w Internecie

Search results

  1. 15 paź 2024 · The typical usage of create_engine () is once per particular database URL, held globally for the lifetime of a single application process. A single Engine manages many individual DBAPI connections on behalf of the process and is intended to be called upon in a concurrent fashion.

  2. 15 paź 2024 · The create_engine() function produces an Engine object based on a URL. The format of the URL generally follows RFC-1738, with some exceptions, including that underscores, not dashes or periods, are accepted within the “scheme” portion.

  3. 15 paź 2024 · Working with Engines and Connections. Basic Usage. Using Transactions. Commit As You Go. Begin Once. Connect and Begin Once from the Engine. Mixing Styles. Setting Transaction Isolation Levels including DBAPI Autocommit. Setting Isolation Level or DBAPI Autocommit for a Connection.

  4. Engine Configuration. The _engine.Engine is the starting point for any SQLAlchemy application. It’s “home base” for the actual database and its DBAPI, delivered to the SQLAlchemy application through a connection pool and a Dialect, which describes how to talk to a specific kind of database/DBAPI combination.

  5. Connection URL Format ¶. See SQLAlchemy’s documentation on Engine Configuration for a complete description of syntax, dialects, and options.

  6. The typical usage of _sa.create_engine() is once per particular database URL, held globally for the lifetime of a single application process. A single _engine.Engine manages many individual DBAPI connections on behalf of the process and is intended to be called upon in a concurrent fashion.

  7. The most generic way is first procure a connection resource, which you get via the Engine.connect() method: connection = engine.connect() result = connection.execute("select username from users") for row in result: print "username:", row['username'] connection.close()

  1. Ludzie szukają również