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
This enhancement started with pull-request by c-martinez SHA: acfd9e7
This new feature uses a VARCHAR field to store the IP addresses of anonymous editors in the DB schema. This may be quite inefficient for querying and indexing on this field.
An alternative solution would be using INET_ATON and INET_NTOA, either from MySQL (may raise compatibility issues with other DB backends) or from the Python code (more likely).
In addition, once the new DB API based on SQLAlchemy is ready, we will have support for PostgreSQL, which has its own data types and functions to handle IP addresses:
This enhancement started with pull-request by c-martinez SHA: acfd9e7
This new feature uses a VARCHAR field to store the IP addresses of anonymous editors in the DB schema. This may be quite inefficient for querying and indexing on this field.
An alternative solution would be using INET_ATON and INET_NTOA, either from MySQL (may raise compatibility issues with other DB backends) or from the Python code (more likely).
In addition, once the new DB API based on SQLAlchemy is ready, we will have support for PostgreSQL, which has its own data types and functions to handle IP addresses:
http://www.postgresql.org/docs/7.4/static/functions-net.html
Therefore, the improved solution must explore transparent support for different DB backends, as well as efficiency (to the extent possible).
The text was updated successfully, but these errors were encountered: