Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
OQGraph v3 tables have fixed structure, the manual says
The CREATE statement must match the format below - any difference will result in an error.
It would be much more user friendly to support assisted discovery and not force the user to specify the table structure at all. Then a user would only need to type, say,
CREATE TABLE oq_graph |
ENGINE=OQGRAPH
|
data_table='oq_backing' origid='origid' destid='destid'; |
Assisted discovery is easy, see federatedx.cc and sequence.cc for examples.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
OQGraph v3 tables have fixed structure, the [[manual|https://mariadb.com/kb/en/oqgraph-examples/]] says "The CREATE statement must match the format below - any difference will result in an error." It would be much more user friendly to support assisted discovery and not force the user to specify the table structure at all. Then a user would only need to type, say, {code:sql} CREATE TABLE oq_graph ENGINE=OQGRAPH data_table='oq_backing' origid='origid' destid='destid'; {code} Assisted discovery is easy, see federatedx.cc and sequence.cc for examples. |
OQGraph v3 tables have fixed structure, the [manual|https://mariadb.com/kb/en/oqgraph-examples/] says "The CREATE statement must match the format below - any difference will result in an error." It would be much more user friendly to support assisted discovery and not force the user to specify the table structure at all. Then a user would only need to type, say, {code:sql} CREATE TABLE oq_graph ENGINE=OQGRAPH data_table='oq_backing' origid='origid' destid='destid'; {code} Assisted discovery is easy, see federatedx.cc and sequence.cc for examples. |
| Description |
OQGraph v3 tables have fixed structure, the [manual|https://mariadb.com/kb/en/oqgraph-examples/] says "The CREATE statement must match the format below - any difference will result in an error." It would be much more user friendly to support assisted discovery and not force the user to specify the table structure at all. Then a user would only need to type, say, {code:sql} CREATE TABLE oq_graph ENGINE=OQGRAPH data_table='oq_backing' origid='origid' destid='destid'; {code} Assisted discovery is easy, see federatedx.cc and sequence.cc for examples. |
OQGraph v3 tables have fixed structure, the [manual|https://mariadb.com/kb/en/oqgraph-examples/] says {quote}The CREATE statement must match the format below - any difference will result in an error.{quote} It would be much more user friendly to support assisted discovery and not force the user to specify the table structure at all. Then a user would only need to type, say, {code:sql} CREATE TABLE oq_graph ENGINE=OQGRAPH data_table='oq_backing' origid='origid' destid='destid'; {code} Assisted discovery is easy, see federatedx.cc and sequence.cc for examples. |
| Assignee | Arjen Lentz [ arjen ] | Andrew McDonnell [ andymc73 ] |
| Fix Version/s | 10.0.12 [ 15201 ] | |
| Fix Version/s | 10.0.11 [ 15200 ] |
| Workflow | defaullt [ 36819 ] | MariaDB v2 [ 42605 ] |
| Fix Version/s | 10.0.13 [ 16000 ] | |
| Fix Version/s | 10.0.12 [ 15201 ] |
| Labels | oqgraph |
| Assignee | Andrew McDonnell [ andymc73 ] | Sergei Golubchik [ serg ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Sergei Golubchik [ serg ] | Andrew McDonnell [ andymc73 ] |
| Attachment | oqgraph_assisted_discovery.patch [ 31302 ] |
| Due Date | 2014-10-06 |
| Assignee | Andrew McDonnell [ andymc73 ] | Sergei Golubchik [ serg ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.1.2 [ 15801 ] | |
| Fix Version/s | 10.0 [ 16000 ] |
| Due Date | 2014-10-06 |
| Component/s | Storage Engine - OQGRAPH [ 10130 ] |
| Status | Stalled [ 10000 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Workflow | MariaDB v2 [ 42605 ] | MariaDB v3 [ 65353 ] |
| Workflow | MariaDB v3 [ 65353 ] | MariaDB v4 [ 132294 ] |