You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possibly a bit tedious, but we only used strings for stricter compatibility with USDA DB, and if we make this work as a mix task or something we should be able to run on future imports of their DB pretty easily too, since they are logically integers, just sometimes zero-prefixed etc, and with internal references using the string based primary keys... ideally we'd preserve those relationships, but frankly dropping the other tables besides those two is also an acceptable option as we're not using any other tables from DB at present. Dealing with future goals like showing aggregate nutritional info for orders would leverage them, but we can deal with that when the time comes.
The text was updated successfully, but these errors were encountered:
Possibly a bit tedious, but we only used strings for stricter compatibility with USDA DB, and if we make this work as a mix task or something we should be able to run on future imports of their DB pretty easily too, since they are logically integers, just sometimes zero-prefixed etc, and with internal references using the string based primary keys... ideally we'd preserve those relationships, but frankly dropping the other tables besides those two is also an acceptable option as we're not using any other tables from DB at present. Dealing with future goals like showing aggregate nutritional info for orders would leverage them, but we can deal with that when the time comes.
The text was updated successfully, but these errors were encountered: