Hi Dan,
thanks for your answer. The UDF only contains functions (the one called in sql
plus two functions called in it). There are no variables outside them and
nothing is declared static. All variables inside the functions are declared
just like double x=0; etc. I am not an expert on C, but
C is not an inherently thread-safe language. Several of the standard
library functions use static data, which gets stepped on during concurrent
operation. Many of those do have thread-safe equivalents on many platforms
such as strtok/strtok_r (the latter being the safe one).
If you are
can you reduce the UDF just to return 1; ?
that should give you a clue what is going on. Random
values usualy point to two suspects
1. mixing 32bit and 64bit
2. using void instead of int
re,
wh
Am 04.11.2012 23:23, schrieb Stefan Kuhn:
Hi all,
I have a weired (for me at least) problem with a
2012/11/04 22:23 +, Stefan Kuhn
select * from table order by udf(column, 'input_value') desc;
For my understanding, this should give the same result always.
But if for your data function udf returns the same for more arguments there
is not enough to fix the order. In that case I have
On Monday 05 November 2012 18:02:28 h...@tbbs.net wrote:
2012/11/04 22:23 +, Stefan Kuhn
select * from table order by udf(column, 'input_value') desc;
For my understanding, this should give the same result always.
But if for your data function udf returns the same for more arguments
InnoDB is _often_ faster than MyISAM. However, blind conversion has _some_
likelihood of causing _some_ queries to be slower. Here is my doc on all the
issues (I could think about):
https://kb.askmonty.org/en/converting-tables-from-myisam-to-innodb/
(Don't worry about being on the MariaDB
