Timeline for Create an SDO_GEOMETRY view from a non-spatial table?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2022 at 21:41 | comment | added | Albert Godfrind | Yes if you are using versions from 12.2 up, you can use a _v2 index type. The internal structures are identical, but the v2 index has more flexibility when dealing with partitioned tables. The original index is restricted to range partitioning. The V2 allows all partitioning methods. The v2 index also has the ability to use a simple btree structure for 2D points instead of a traditional rtree. | |
| May 12, 2022 at 22:40 | comment | added | User1974 | Should the index type be mdsys.spatial_index_v2 instead of mdsys.spatial_index? | |
| Dec 18, 2020 at 16:25 | history | bounty ended | User1974 | ||
| Dec 16, 2020 at 7:50 | comment | added | User1974 | Related: Materialized view with FAST refresh on remote table: How to include a SHAPE column? ... Function-based spatial index: Use sdo_geometry() constructor instead of custom function? ... SDO_GEOMETRY view in ArcGIS Desktop | |
| Aug 14, 2020 at 6:47 | comment | added | Albert Godfrind | Yes the index is always created on the table. Creating indexes on views is actually not allowed. The idea of using a view is so as to make everything transparent: make it look as if we had a table with full spatial types instead of x and y columns. | |
| Aug 12, 2020 at 9:32 | comment | added | zlinks | Hi, isn't the index created on the initial TABLE? In the case of the example on the Customer table. Facing a very similar issue | |
| Oct 7, 2015 at 8:30 | history | edited | Albert Godfrind | CC BY-SA 3.0 |
added 334 characters in body
|
| Oct 7, 2015 at 8:14 | history | edited | Albert Godfrind | CC BY-SA 3.0 |
Added explanations on how to use the default geometry constructor instead of a custom function.
|
| Oct 7, 2015 at 8:02 | comment | added | Albert Godfrind | Travis: "I don't think you actually NEED the function, but is does clean things up quite a bit.". You are correct. You can actually directly use the SDO_GEOMETRY constructor (which is effectively a deterministic function). I have updated the response to include that option. | |
| Oct 5, 2015 at 20:33 | comment | added | eblondel | Many thanks for this! For those that use oracle with geoserver, i confirm this approach works very well (tested with Geoserver 2.5.1). | |
| May 7, 2014 at 14:36 | history | edited | Albert Godfrind | CC BY-SA 3.0 |
added 286 characters in body
|
| May 7, 2014 at 14:32 | comment | added | Albert Godfrind | For NULL values, the function needs to handle that. I have updated my reply to include that. | |
| May 7, 2014 at 13:01 | comment | added | Erik L | Any ideas on if the lat/lon columns have null values? Should a view be created, or should the function handle that? | |
| May 5, 2014 at 19:18 | vote | accept | Erik L | ||
| Apr 12, 2014 at 0:59 | comment | added | travis | I don't think you actually NEED the function, but is does clean things up quite a bit. | |
| Apr 10, 2014 at 17:26 | comment | added | Erik L | That is brilliant, I am working right now to see if it works. | |
| Apr 10, 2014 at 7:25 | history | answered | Albert Godfrind | CC BY-SA 3.0 |