[MDEV-8986] wrong geometry type Created: 2015-10-22 Updated: 2021-01-16 Resolved: 2021-01-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | GIS |
| Affects Version/s: | 10.0.21 |
| Fix Version/s: | 10.1.26, 10.0.32, 10.2.10, 10.3.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Pavel Dvorak | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
debian x64 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
server returns random column type
|
| Comments |
| Comment by Elena Stepanova [ 2015-10-23 ] | |||||
|
I am getting
no matter how many times I try. Are you just running describe geozone from MySQL client connection over and over again? Or are you reconnecting everytime? Or do you use something other than MySQL client? Could you please attach your cnf file(s) and specify which binaries and which Debian you use? Is there anything suspicious in the error log? | |||||
| Comment by Pavel Dvorak [ 2015-10-24 ] | |||||
|
i used both php script and console | |||||
| Comment by Elena Stepanova [ 2015-10-25 ] | |||||
|
I ran DESCRIBE 10K times, but still haven't got even a single 'polygon' as a type. Could you please paste the entire output, from when you open a client session, with full DESCRIBE result (all columns), all attempts up to and including the one that returns 'polygon', and further until it switches back to 'geometry'? Are you sure there is no other connection that alters the table in parallel? Is it a newly created table, or did it come from a previous MariaDB version? Is it reproducible after you re-create the table, or on another table with a different name? Could you maybe provide the frm file on which you get this issue? Thanks. | |||||
| Comment by Pavel Dvorak [ 2015-10-27 ] | |||||
|
no other connection | |||||
| Comment by Elena Stepanova [ 2015-10-27 ] | |||||
|
I've removed my previous comment – sorry, did not notice at first that you have already attached files. Are these the old ones? | |||||
| Comment by Pavel Dvorak [ 2015-10-27 ] | |||||
|
yes | |||||
| Comment by Pavel Dvorak [ 2015-11-25 ] | |||||
|
what feedback? | |||||
| Comment by Elena Stepanova [ 2015-11-25 ] | |||||
|
dvorak, you received a notification because I removed the flag "needs_feedback" which was left there by mistake (I know, it's not obvious from the generated notifications). | |||||
| Comment by Pavel Dvorak [ 2015-11-25 ] | |||||
|
this would be a problem, it's production server, gps monitoring, it has 500GB | |||||
| Comment by Elena Stepanova [ 2015-11-25 ] | |||||
|
Do you happen to remember which version of MySQL it was created with? | |||||
| Comment by Pavel Dvorak [ 2015-11-25 ] | |||||
|
it was 5.6 dont' know which one | |||||
| Comment by Piotr Labudda [ 2016-11-15 ] | |||||
|
BUG with describe table for geometry fields exists in MariaDB 5.5.0 and 10.1 Steps to reproduce this bug: – 1. create test table with geometry field: – 2. insert some date: – test 1 - simple query: – test 2 - add another field to where: – repair table fix field type: Question is: Why select query can brake table structure returned by describe or show fields from? | |||||
| Comment by Elena Stepanova [ 2021-01-16 ] | |||||
|
The bug was fixed in 10.0.32 and corresponding higher versions by this commit:
|