Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Allow userdb.usernick to be NULL
Otherwise guest checkout doesn't work.
- Loading branch information
Showing
3 changed files
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57f71fe
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.
This is necessary because of Interchange's pattern of first inserting a row with 1 or 2 columns, then coming back a second time to flesh out the rest of the columns.
The Interchange New-Account process thus fails to set a value for the
usernick
field, which causes errors such as:set_row error as called by Vend::Table::DBI: DBD::Pg::db do failed: ERROR: null value in column "usernick" violates not-null constraint
This is not an issue with MySQL, go figure.
In an ideal world, we would fix the underlying Interchange "insert" method, because we value database integrity -- if you are writing a NULL to the
usernick
column, you are doing it wrong... -- but this is the acceptable solution for now.