- Posts: 687
[2.12.9 Bugs] Property / RMS - lat - lng DB columns
- joomleb
- Topic Author
- Offline
Less
More
2 years 7 months ago - 2 years 7 months ago #19262
by joomleb
[2.12.9 Bugs] Property / RMS - lat - lng DB columns was created by joomleb
Hi guys,
PHP 7.4.30 + MariaDB 10.5.15
1 - #_rms_properties
Furthermore lat and lng columns are set with “Type: FLOAT”, while it should be “Type: DECIMAL”.
You have yet fixed it in the recent past for the Properties
For all - #_sr_reservation_assets + #_rms_properties (and #_sr_experiences)
2 - About Length/Values decimals
lat / lng columns are set as “10,6”, by using only 6 decimals. But:
- being that the number of relevant decimal places used in numbers seems does not affect performance
- the most used decimals value is 8 > gis.stackexchange.com/a/8674
- latitude is 2 digits, while longitude is 3 > dba.stackexchange.com/questions/107089/d...cation-data-in-mysql
- The Decimal point and (for negative numbers) the "-" sign are not counted > mariadb.com/kb/en/decimal/
They can be set as: Lat 10,8 - Lng 11,8
3 - lat and lng as empty / blank
I should be able to save Property / Experience / Restaurant latitude and longitude as empty / blank, because:
- if the Partner does not want to show his Property in the Maps he is free to leave the lat / lng fields empty
- if a forced default “0.000000” value is input, the operation Maps is compromised for all the Users showing nonexistent points in the middle of the Earth Anyway, this seems to not be enough and, if Latitude / Longitude fields are empty, I can save the item, but fields are always filled as 0,000000 value.
Do you agree ?
Right now lat and lng columns are set with “Default: As defined - 0.000000”, I tested them with “Default: none - Null: not selected”, but without success.
We investigated on it and these are some useful information:
- stackoverflow.com/questions/8965426/what...-checkbox-null-mysql
- stackoverflow.com/a/8559691
...
PHP 7.4.30 + MariaDB 10.5.15
1 - #_rms_properties
Furthermore lat and lng columns are set with “Type: FLOAT”, while it should be “Type: DECIMAL”.
You have yet fixed it in the recent past for the Properties
For all - #_sr_reservation_assets + #_rms_properties (and #_sr_experiences)
2 - About Length/Values decimals
lat / lng columns are set as “10,6”, by using only 6 decimals. But:
- being that the number of relevant decimal places used in numbers seems does not affect performance
- the most used decimals value is 8 > gis.stackexchange.com/a/8674
- latitude is 2 digits, while longitude is 3 > dba.stackexchange.com/questions/107089/d...cation-data-in-mysql
- The Decimal point and (for negative numbers) the "-" sign are not counted > mariadb.com/kb/en/decimal/
They can be set as: Lat 10,8 - Lng 11,8
3 - lat and lng as empty / blank
I should be able to save Property / Experience / Restaurant latitude and longitude as empty / blank, because:
- if the Partner does not want to show his Property in the Maps he is free to leave the lat / lng fields empty
- if a forced default “0.000000” value is input, the operation Maps is compromised for all the Users showing nonexistent points in the middle of the Earth Anyway, this seems to not be enough and, if Latitude / Longitude fields are empty, I can save the item, but fields are always filled as 0,000000 value.
Do you agree ?
Right now lat and lng columns are set with “Default: As defined - 0.000000”, I tested them with “Default: none - Null: not selected”, but without success.
We investigated on it and these are some useful information:
- stackoverflow.com/questions/8965426/what...-checkbox-null-mysql
- stackoverflow.com/a/8559691
...
Last edit: 2 years 7 months ago by joomleb.
Please Log in or Create an account to join the conversation.
- joomleb
- Topic Author
- Offline
Less
More
- Posts: 687
2 years 7 months ago - 2 years 7 months ago #19264
by joomleb
Replied by joomleb on topic [2.12.9 Bugs] Property / RMS - lat - lng DB columns
...(I had to split the post for the links)
...
- mariadb.com/kb/en/null-values/
- stackoverflow.com/a/54187551
- stackoverflow.com/a/57725225
- stackoverflow.com/a/21593490
- laravel.io/forum/06-21-2016-how-to-store...l-in-a-decimal-field
It seems like that the workaround have to found on coding.
Please, Can you point us on the right way to fix it ?
...
- mariadb.com/kb/en/null-values/
- stackoverflow.com/a/54187551
- stackoverflow.com/a/57725225
- stackoverflow.com/a/21593490
- laravel.io/forum/06-21-2016-how-to-store...l-in-a-decimal-field
It seems like that the workaround have to found on coding.
Please, Can you point us on the right way to fix it ?
Last edit: 2 years 7 months ago by joomleb.
Please Log in or Create an account to join the conversation.
Moderators: solidres