sqlExport: transactions table primary key is causing data loss #2

Closed
opened 2020-03-04 14:13:22 -05:00 by adam.goldsmith · 1 comment

Timestamp, unsuprisingly, is not a valid key for that table, but I'm pretty sure nothing is. Maybe just declare the whole table as a key? (but we can't because non-fixed length fields cannot be keys)

Timestamp, unsuprisingly, is not a valid key for that table, but I'm pretty sure nothing is. Maybe just declare the whole table as a key? (but we can't because non-fixed length fields cannot be keys)
adam.goldsmith added the
bug
label 2020-03-04 14:13:22 -05:00
Author
Owner

Fixed for real in e49a894e45

Fixed for real in e49a894e45
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: CMS/memberPlumbing#2
No description provided.