Rewrite: BigIntegerField for Discord Snowflake IDs #49

New Issue

corbz · 2024-08-20T13:36:03Z

corbz commented

2024-08-20 13:36:03 +00:00

Required for #47
This may be a breaking change.

Currently using CharField for Discord Snowflake IDs due to an sqlite bug with the PositiveBigIntegerField that rounds the IDs down when storing.

Try out the BigIntegerField and check against sqlite for issues, it makes more sense to use than the CharField.

Required for #47 This may be a breaking change. Currently using `CharField` for Discord Snowflake IDs due to an sqlite bug with the `PositiveBigIntegerField` that rounds the IDs down when storing. Try out the `BigIntegerField` and check against sqlite for issues, it makes more sense to use than the `CharField`.

corbz added the

enhancement

label 2024-08-20 13:36:03 +00:00

corbz self-assigned this 2024-08-20 13:36:03 +00:00

corbz added this to the PYRSS project 2024-08-20 13:36:03 +00:00

corbz commented

2024-10-08 08:26:31 +00:00

It's not an sqlite bug, but an issue with the way js and django rest framework's json parser handles big integers.

I've implemented a custom json parser that converts large integers to strings.

It's not an sqlite bug, but an issue with the way js and django rest framework's json parser handles big integers. I've implemented a custom json parser that converts large integers to strings.

corbz closed this issue

2024-10-08 08:26:31 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: corbz/PYRSS-Website#49