-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try to handle changes to type definitions #43
Changes from 7 commits
fd399fb
d3a7090
a2846e4
3ebcc6b
fae67d8
6414fe1
b55b87d
5d49f4d
3431d24
0f422eb
363123f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,7 +8,7 @@ | |
from postgres.cursors import TooFew, TooMany, SimpleDictCursor | ||
from postgres.orm import ReadOnly, Model | ||
from psycopg2 import InterfaceError, ProgrammingError | ||
from pytest import raises | ||
from pytest import mark, raises | ||
|
||
|
||
DATABASE_URL = os.environ['DATABASE_URL'] | ||
|
@@ -334,6 +334,32 @@ def test_unregister_unregisters_multiple(self): | |
self.db.unregister_model(self.MyModel) | ||
assert self.db.model_registry == {} | ||
|
||
def test_add_column_doesnt_break_anything(self): | ||
self.db.run("ALTER TABLE foo ADD COLUMN boo text") | ||
one = self.db.one("SELECT foo.*::foo FROM foo WHERE bar='baz'") | ||
assert one.boo is None | ||
|
||
def test_replace_column_different_type(self): | ||
self.db.run("CREATE TABLE grok (bar int)") | ||
self.db.run("INSERT INTO grok VALUES (0)") | ||
class EmptyModel(Model): pass | ||
self.db.register_model(EmptyModel, 'grok') | ||
# Add a new column then drop the original one | ||
self.db.run("ALTER TABLE grok ADD COLUMN biz text NOT NULL DEFAULT 'x'") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Isn't There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry, this is |
||
self.db.run("ALTER TABLE grok DROP COLUMN bar") | ||
# The number of columns hasn't changed but the names and types have | ||
one = self.db.one("SELECT grok.*::grok FROM grok LIMIT 1") | ||
assert one.biz == 'x' | ||
assert not hasattr(one, 'bar') | ||
|
||
@mark.xfail(raises=AttributeError) | ||
def test_replace_column_same_type(self): | ||
self.db.run("ALTER TABLE foo ADD COLUMN biz int NOT NULL DEFAULT 0") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So what's going on here, then? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That looks a lot like adding a There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In that case, I'm more confused. It seems like there's some interaction between the number and types of the columns we're adding and dropping here, but I'm not getting it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test fails because the number of columns is the same (so the length test doesn't detect the change) and the types of the old and new columns are compatible (so there is no type error to catch). |
||
self.db.run("ALTER TABLE foo DROP COLUMN bar") | ||
one = self.db.one("SELECT foo.*::foo FROM foo LIMIT 1") | ||
assert one.biz == 0 | ||
assert not hasattr(one, 'bar') | ||
|
||
|
||
# cursor_factory | ||
# ============== | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did we get this line from, and why do we not call it in the normal course of operation? Why are we doing something in this case that we don't otherwise do? Don't we need to configure the class when it's first instantiated? Why am I not seeing that in our code? Is it in
psycopg2
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's
CompositeCaster
onmaster
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, we're calling
_from_db
, which is a constructor classmethod, and then we're overwriting all possible attributes on ourself with the corresponding attributes from the new instance.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clarified in 0f422eb.