[MDEV-7371] DEFAULT values for CONNECT tables Created: 2014-12-25  Updated: 2014-12-26  Due: 2015-01-25  Resolved: 2014-12-26

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.0.15
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Federico Razzoli Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

From the error I get in this test case, I suppose that CONNECT doesn't support default values (the error is a bit obscure). However, supporting default values would be useful at least for PROXY tables built on non-CONNECT tables.

MariaDB [test]> CREATE OR REPLACE TABLE abc (
 
    -> c INT NOT NULL DEFAULT 1
 
    -> ) ENGINE = InnoDB;
 
Query OK, 0 rows affected (0.48 sec)
 
 
 
MariaDB [test]> CREATE OR REPLACE TABLE conn (
 
    -> c INT NOT NULL DEFAULT 1
 
    -> )
 
    -> ENGINE = CONNECT
 
    -> TABLE_TYPE = PROXY
 
    -> TABNAME = abc
 
    -> OPTION_LIST = 'user=root,password=root';
 
Query OK, 0 rows affected (0.09 sec)
 
 
 
MariaDB [test]> INSERT INTO abc VALUES (DEFAULT);
 
Query OK, 1 row affected (0.08 sec)
 
 
 
MariaDB [test]> INSERT INTO conn VALUES (DEFAULT);
 
ERROR 1296 (HY000): Got error 174 'COLBLK SetBuffer: undefined Access Method' from CONNECT

If I retry the test case without specifying the columns definitions for conn table, I get the following error:

ERROR 1364 (HY000): Field 'c' doesn't have a default value

 Comments   
Comment by Elena Stepanova [ 2014-12-25 ]

Works okay for me:

MariaDB [test]> CREATE OR REPLACE TABLE abc (
 
    ->   c INT NOT NULL DEFAULT 1
 
    -> ) ENGINE = InnoDB;
 
Query OK, 0 rows affected (0.45 sec)
 
 
 
MariaDB [test]> CREATE OR REPLACE TABLE conn (
 
    ->   c INT NOT NULL DEFAULT 1
 
    -> )
 
    -> ENGINE = CONNECT
 
    -> TABLE_TYPE = PROXY
 
    -> TABNAME = abc
 
    -> OPTION_LIST = 'user=root,password=root';
 
Query OK, 0 rows affected (0.02 sec)
 
 
 
MariaDB [test]> 
MariaDB [test]> INSERT INTO abc VALUES (DEFAULT);
 
Query OK, 1 row affected (0.00 sec)
 
 
 
MariaDB [test]> 
MariaDB [test]> INSERT INTO conn VALUES (DEFAULT);
 
Query OK, 1 row affected (0.07 sec)
 
 
 
MariaDB [test]> select @@version;
 
+-----------------+
 
| @@version       |
 
+-----------------+
 
| 10.0.15-MariaDB |
 
+-----------------+
 
1 row in set (0.00 sec)

What am I missing?

Comment by Federico Razzoli [ 2014-12-26 ]

I don't know. In case it matters, I used the tarball on Debian

Comment by Elena Stepanova [ 2014-12-26 ]

Which Debian?

Also, please attach your SHOW VARIABLES from the session where the failure happens. Thanks.

Comment by Federico Razzoli [ 2014-12-26 ]

Debian 7, but I cannot repeat the bug anymore. Sorry.

(If it happens again, I'll immediately do a SHOW VARIABLES)

Comment by Elena Stepanova [ 2014-12-26 ]

Okay, I'm closing it for now, we'll re-open it if you have the problem again.

Generated at Thu Feb 08 07:19:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.