Skip to content
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

Complications due to EmailField width handling #6

Open
dvogel opened this issue Oct 10, 2013 · 0 comments
Open

Complications due to EmailField width handling #6

dvogel opened this issue Oct 10, 2013 · 0 comments
Assignees

Comments

@dvogel
Copy link
Contributor

dvogel commented Oct 10, 2013

MySQL silently truncates character fields while PostgreSQL raises a DatabaseError exception. Since the key is queued for replication without a round trip to the database, this can cause problems for api servers using PostgreSQL while syncing with a hub that uses MySQL.

  • The EmailField max_length setting should be 254 (currently 75) on both the hub and the server in order to mitigate the truncation.
  • The queued task that replicates the key should pull the key from the database. This will ensure that the api servers have the same email address as the hub does, truncated or otherwise.
@ghost ghost assigned dvogel Oct 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant