Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>UPDATE</strong>: Tested and fixed</p> <p>Instead of making a new connection and re-creating your database every time (slow), you can use subsessions and do a rollback after each test.</p> <p>The connection are reused, so this also fix the problem you're having.</p> <pre><code>class TestCase(Base): @classmethod def setUpClass(cls): cls.app = create_app(MyConfig()) cls.client = cls.app.test_client() cls._ctx = cls.app.test_request_context() cls._ctx.push() db.create_all() @classmethod def tearDownClass(cls): db.session.remove() db.drop_all() db.get_engine(cls.app).dispose() def setUp(self): self._ctx = self.app.test_request_context() self._ctx.push() db.session.begin(subtransactions=True) def tearDown(self): db.session.rollback() db.session.close() self._ctx.pop() </code></pre> <p>If you need to also make an instance of the application for each test, just add it to the <code>setUp</code> method but leave it also in <code>setUpClass</code>.</p> <p>Full test example below requires flask_sqlalchemy and psycopg2. Create a test database named "test" and set its connection limit to 15.</p> <pre><code>from flask import Flask from flask.ext.sqlalchemy import SQLAlchemy from unittest import TestCase as Base db = SQLAlchemy() def create_app(config=None): app = Flask(__name__) app.config.from_object(config) db.init_app(app) return app class MyConfig(object): SQLALCHEMY_DATABASE_URI = "postgresql://localhost/test" TESTING = True class TestCase(Base): @classmethod def setUpClass(cls): cls.app = create_app(MyConfig()) cls.client = cls.app.test_client() cls._ctx = cls.app.test_request_context() cls._ctx.push() db.create_all() @classmethod def tearDownClass(cls): db.session.remove() db.drop_all() def setUp(self): self._ctx = self.app.test_request_context() self._ctx.push() db.session.begin(subtransactions=True) def tearDown(self): db.session.rollback() db.session.close() self._ctx.pop() class TestModel(TestCase): def test_01(self): pass def test_02(self): pass def test_03(self): pass def test_04(self): pass def test_05(self): pass def test_06(self): pass def test_07(self): pass def test_08(self): pass def test_09(self): pass def test_10(self): pass def test_11(self): pass def test_12(self): pass def test_13(self): pass def test_14(self): pass def test_15(self): pass def test_16(self): pass if __name__ == "__main__": import unittest unittest.main() </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POFlask unittest and sqlalchemy using all connections
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJuan-Pablo Scaletti
    1. USJuan-Pablo Scaletti
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COsetUpClass is run before create_app() is called so there is no db initialized yet. Although this is interesting for unittest performance. Even if it did work I think I would still have some sort of issue in my code not closing connections. This would just be a workaround to a problem that might get exposed in production.
      singulars
      1. PO
      1. USAdam P
    2. COFixed and added a full example.
      singulars
      1. PO
      1. USJuan-Pablo Scaletti
    3. COJuan-Pablo, Thank you very much for taking the time to answer. I don't care about points at all but I answered my own question, so the next person wouldn't be as frustrated. I believe your solution is maybe an overall better solution to the problem as it solves it and clearly makes the tests run waaaay faster, but I was unable to get it to work either. I could run what you have but, I was violating unique constraints on my database since the database wasn't really rolling back, between tests. I will continue to research. Thank you for your time
      singulars
      1. PO
      1. USAdam P
 

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