maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #07917
Re: [Commits] Rev 4358: MDEV-7113 difference between check_vcol_func_processor and check_partition_func_processor in lp:~maria-captains/maria/5.5
Hi, Sergey!
On Nov 19, Sergey Petrunia wrote:
> Hi Sergei,
>
> * what about persistent virtual columns? Do we still support
> environment-dependent virtual functions for those?
I've explained that in a comment - I was mostly trying to fix crashes,
like that one with FROM_UNIXTIME. I'm hesitant to reduce the set of
supported functions in GA version. I think we can do it in 10.1 or 10.2.
> * the behavior of current solution is not deterministic:
>
> thread1> select @@time_zone;
> +-------------+
> | @@time_zone |
> +-------------+
> | SYSTEM |
> +-------------+
> 1 row in set (0.00 sec)
>
> thread1> create table t2 ( a varchar(32), b int, v varchar(100) as (from_unixtime(b)));
> Query OK, 0 rows affected (0.28 sec)
>
> thread1> insert into t2 (a,b) values ('local-tz-23-11', unix_timestamp());
> Query OK, 1 row affected (0.04 sec)
>
> thread1> select * from t2;
> +----------------+------------+---------------------+
> | a | b | v |
> +----------------+------------+---------------------+
> | local-tz-23-11 | 1416427891 | 2014-11-19 23:11:31 |
> +----------------+------------+---------------------+
> 1 row in set (0.00 sec)
>
> thread2> set time_zone='Europe/Helsinki';
> Query OK, 0 rows affected (0.00 sec)
>
> thread2> select * from t2;
> +----------------+------------+---------------------+
> | a | b | v |
> +----------------+------------+---------------------+
> | local-tz-23-11 | 1416427891 | 2014-11-19 23:11:31 |
> +----------------+------------+---------------------+
> 1 row in set (0.00 sec)
>
> thread2> flush tables;
> Query OK, 0 rows affected (0.00 sec)
>
> thread2> select * from t2;
> +----------------+------------+---------------------+
> | a | b | v |
> +----------------+------------+---------------------+
> | local-tz-23-11 | 1416427891 | 2014-11-19 22:11:31 |
> +----------------+------------+---------------------+
> 1 row in set (0.00 sec)
Yes, I have that in the test. For FROM_UNIXTIME, for division, and for
MONTHNAME, DAYNAME and DATE_FORMAT.
> Is this really ok? Maybe, it makes sense to use some some "default"
> (e.g. global variables) environment on the non-deterministic
> virtual column functions?
Not that's not really ok, but... see above.
I've only changed FROM_UNIXTIME not to crash (using the same approach
that MONTHNAME and DAYNAME were already using), and fixed DATE_FORMAT to
return the same as MONTHNAME and DAYNAME.
I don't like the current behavior and I've shown that it's buggy in the
test. But I don't think we can change it in 5.5 or 10.0
> Or, make these functions always fetch the environment from the
> current thread?
Calling current_thd from val* methods?
Regards,
Sergei
Follow ups
References