-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix #611: ContactSchema
now reflects what is stored in database
#711
Conversation
f41c77a
to
1696c47
Compare
1696c47
to
4c4c853
Compare
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.
instances coming the database (
*Table*
schemas)
I saw this and was slightly thrown by the naming introduced in d0e27b0, since there's no "Contact" table in the database. Is this to mean "a contact comprised entirely of *TableSchema
objects?
Because there is not contact table in the database :) This reverts commit d0e27b0.
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.
Looks good! Some of the testing methodology does pain me, but hopefully we'll continue to make improvements here as we improve our schemas
Co-authored-by: grahamalama <gbeckley@mozilla.com>
This PR clarifies a bit that we are sometimes dealing with instances coming the database (
*Table*
schemas) and instances coming as input (*In*
schemas).It fixes bug #611 where timestamps were dropped during the Acoustinc sync process (because objects from the database were casted to input objects that don't have timestamp fields)