Database consistency issues
Konstantin Ryabitsev
konstantin at linuxfoundation.org
Thu Aug 9 01:47:32 AEST 2018
On Thu, Aug 09, 2018 at 01:16:25AM +1000, Daniel Axtens wrote:
>>> SELECT id, submission_id FROM patchwork_comment WHERE
>> submission_id=9896319;
>> +----------+---------------+
>> | id | submission_id |
>> +----------+---------------+
>> | 20810589 | 9896319 |
>> +----------+---------------+
>> 1 row in set (0.00 sec)
>>
>> MariaDB [KORG_PATCHWORK]> SELECT * FROM patchwork_submission WHERE
>> id=9896319;
>> Empty set (0.00 sec)
>
>Right, well this is definitely the most terrifying start to any email I
>have received since starting as one of the patchwork maintainers!
Haha, sorry, I should have prefixed this with "I'm not seeing any data
loss." :)
>I will prepare a patch that adds the foreign keys.
Thanks! I know they are in place for the pgsql side of things, since the
lore.kernel.org/patchwork instance is using postgresql. So, it was
either a difference between db implementations, or a side-effect of
migration.
Best,
-K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20180808/e1d4a1fd/attachment.sig>
More information about the Patchwork
mailing list