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
I don't know if this is a real "bug" of this module or a bad design choice in framework.
The ID column is serial8 which is a bigint (64bit).
All other ID columns (has_one, many_many) are integers (32bit).
I think instead of using DBInt for many_many and DBPolymorphicForeignKey they should use DBForeignKey internally, this would allow to use a custom schema for foreign keys.
The text was updated successfully, but these errors were encountered:
Can you please also explain specifically whether this is causing problems for you, and what those problems are? I get that these types aren't inconsistent and it might be better if they were... I'm just trying to understand if that's a bug per se or just something that could be improved.
Can you please also explain specifically whether this is causing problems for you, and what those problems are?
No real problem yet. I don't even know how postgres handles a compare between two different integer types. But I had performance issues with Enum and a Varchar with different collation on MariaDB Databases in the past.
I have to migrate my database from MariaDB to PostgreSQL and I have some tables which have the potential to grow realy fast and even if I don't think that they will reach the maximal value of 32 bit in the near future, I liked the fact that the IDs in the PostgreSQL driver are already 64 bit based, until I saw that the references are still 32 bit.
Okay, cool. Thanks for that context. Because this is an enhancement rather than a bug, it's not covered under the current support model for this module.
As mentioned above we're looking for maintainers, so if you're interested in looking after this module and implementing that enhancement I recommend checking out the link in my previous comment.
I don't know if this is a real "bug" of this module or a bad design choice in framework.
The ID column is
serial8
which is abigint
(64bit).All other ID columns (has_one, many_many) are integers (32bit).
I think instead of using
DBInt
for many_many andDBPolymorphicForeignKey
they should useDBForeignKey
internally, this would allow to use a custom schema for foreign keys.The text was updated successfully, but these errors were encountered: