Skip to content
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

Jump to bottom

View spatial fields as WKT doesn't work #14121

Closed
aroralakshya opened this issue Mar 24, 2018 · 0 comments · Fixed by #14125
Closed

View spatial fields as WKT doesn't work #14121

aroralakshya opened this issue Mar 24, 2018 · 0 comments · Fixed by #14125
Assignees
@MauricioFauth
Milestone
4.8.1

Comments

@aroralakshya
Copy link
Contributor

aroralakshya commented Mar 24, 2018 •
edited by ibennetch

Steps to reproduce

  1. make a table with spatial fields
`CREATE TABLE t (
 point POINT DEFAULT NULL
) ENGINE=InnoDB;

INSERT INTO `t` (`point`) VALUES (NULL), (PointFromText('POINT(1 1)'));`
  1. View the table contents as wkt(well known text) in the options menu.

Expected behaviour

Blank values in the corresponding cell.

Actual behaviour

Should display the cell as wkt

Server configuration

Operating system:
ubuntu 16.04

Web server:
Apache/2.4.29 (Unix)

Database:
10.1.30-MariaDB

PHP version:
7.1.14

phpMyAdmin version:
4.8.0-dev
This was referenced Mar 24, 2018
Closed
Merged
MauricioFauth pushed a commit that referenced this issue May 12, 2018
@aroralakshya @MauricioFauth
Fix for issues with spatial fields (#14125)
9231620 
*  Fix for issues with spatial fields

Fixes the following issues:

1.    #14068 SPATIAL fields with no unique index/autoincrement error when clicking
      This error occurs when there is no unique column to uniquely identify a tuple. I've disabled the geomtery view and made view as wkt the default view in such cases.

2.    #14121 View spatial fields as WKT doesn't work

1.    #14067 IS NULL search operator produces no WHERE SQL with spatial fields

Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>

* Fix for issues with spatial fields
This commit fixes view as BINARY not working in the previous commit.
Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>

* Fix for issues with spatial fields

Fixes typo in previous commits.

Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>
@MauricioFauth MauricioFauth self-assigned this May 12, 2018
MauricioFauth pushed a commit that referenced this issue May 12, 2018
@aroralakshya @MauricioFauth
Fix for issues with spatial fields (#14125)
0da5857 
*  Fix for issues with spatial fields

Fixes the following issues:

1.    #14068 SPATIAL fields with no unique index/autoincrement error when clicking
      This error occurs when there is no unique column to uniquely identify a tuple. I've disabled the geomtery view and made view as wkt the default view in such cases.

2.    #14121 View spatial fields as WKT doesn't work

1.    #14067 IS NULL search operator produces no WHERE SQL with spatial fields

Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>

* Fix for issues with spatial fields
This commit fixes view as BINARY not working in the previous commit.
Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>

* Fix for issues with spatial fields

Fixes typo in previous commits.

Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>
(cherry picked from commit 9231620)
Signed-off-by: Maurício Meneghini Fauth <mauriciofauth@gmail.com>
@MauricioFauth MauricioFauth added this to the 4.8.1 milestone May 12, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MauricioFauth MauricioFauth

Labels
None yet
Projects
None yet
Milestone
4.8.1
Development

Successfully merging a pull request may close this issue.

Fix for issues with spatial fields
2 participants
@MauricioFauth @aroralakshya