Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

change nomenclature from participant_id to username #287

Closed
chadwhitacre opened this issue Sep 13, 2012 · 3 comments
Closed

change nomenclature from participant_id to username #287

chadwhitacre opened this issue Sep 13, 2012 · 3 comments

Comments

@chadwhitacre
Copy link
Contributor

This is a db schema change. I constantly catch myself calling it username but I want to stay consistent.

@chadwhitacre
Copy link
Contributor Author

Surfaced while working on #80.

chadwhitacre added a commit that referenced this issue Apr 5, 2013
I sort of did this one with the blast shield down. I haven't even run
the tests yet. The sorts of things I changed:

 - SQL {elsewhere,exchanges}.participant_id => .participant
 - SQL participants.id => .username
 - ORM {user,participant,self}.id => .username
@chadwhitacre
Copy link
Contributor Author

Does SQLAlchemy special case id attributes or something? I have a hunch we're getting caught in some magic because I'm trying to use username as the primary key and id as a unique serial though not the primary key.

chadwhitacre added a commit that referenced this issue Apr 7, 2013
chadwhitacre added a commit that referenced this issue Apr 7, 2013
@chadwhitacre
Copy link
Contributor Author

No magic. I needed to update the Tip model.

chadwhitacre added a commit that referenced this issue Apr 7, 2013
chadwhitacre added a commit that referenced this issue Apr 7, 2013
I accidentally added mixpanel code on the username branch (see #287 and
 #680) by creating that branch while on the mixpanel branch. Now the
username/id stuff is deployed and our app is looking for MIXPANEL_TOKEN,
but I'm not ready to send stuff to Mixpanel yet. This simply comments
out the mixpanel calls I had added so far.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant