New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some int columns are being created as bigint in PostgreSQL #213
Comments
The
According to the Drupal documentation, this should result in an I found this old (closed) issue in the Drupal core queue - not sure if it's related: https://www.drupal.org/project/drupal/issues/256001 |
This is what I see in my local PostgreSQL test instance (running in Docker):
Notably, both the |
OK, learned a bit more about this... PostgreSQL does not support https://stackoverflow.com/questions/20810134/why-unsigned-integer-is-not-available-in-postgresql So... we're going to need to reassess the Fraction module's support for PostgreSQL. |
I opened an issue in the Fraction module queue, linked back to this one: https://www.drupal.org/project/fraction/issues/3093326 |
Just remembered this related issue: https://www.drupal.org/project/fraction/issues/2729315 |
The main issue is: anyone who has installed farmOS on PostgreSQL will have I'm not sure if there's anything we can do about it, unfortunately. The only way to avoid that error popping up would be to officially increase the size of |
Should also check to see if |
This has been fixed in the Fraction module: https://www.drupal.org/project/fraction/issues/2729315 As well as in the |
Some int columns are being created as bigint in PostgreSQL. This was discovered by @Skipper-is .
It is particularly an issue with fraction denominator fields, which are specifically supposed to be
int
s. See https://drupal.org/project/fraction.@Skipper-is discovered this when he was trying to migrate his database from PostgreSQL to MySQL, and discovered that the PostgreSQL database was using
bigint
for theid
anddenominator
columns in the{farm_sensor_data}
table.The text was updated successfully, but these errors were encountered: