On 11.03.2016 15:45, Alexander Barkov wrote:
> FYI, I have added a new task for this:
>
> https://jira.mariadb.org/browse/MDEV-9711
>
Alexander,
I couldn't resist taking a quick look into the sources.
- I have found my_hash_sort_utf8 in strings/ctype-utf8.c and am convinced that
the change is
On 11.03.2016 15:45, Alexander Barkov wrote:
> FYI, I have added a new task for this:
>
> https://jira.mariadb.org/browse/MDEV-9711
>
Alexander, not sure if my question makes any sense, but what about the _cs
collations? Like latin1_general_cs, latin2_czech_cs? Don't we like to have
these, too
Hello,
A new question has been asked in "News and Information" by stuart_zurcher_g.
Please answer it at
http://mariadb.com/kb/en/mariadb-10112-mysql_install_db-aborts-on-unkown-file-test/
as the person asking the question may not be subscribed to the mailing list.
-
> Hi Binarus,
>
> I see 3 options here:
>
> 1) MariaDB captains can help you implementing this, we always welcome
> contributions and Alexander already point you where to start.
>
> 2) You really need this feature and can switch to MariaDB, please contact one
> of our sale reps to quote you
On 11.03.2016 15:45, Alexander Barkov wrote:
> FYI, I have added a new task for this:
>
> https://jira.mariadb.org/browse/MDEV-9711
Thank you very much! Exactly what I hoped ...
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : mari
Hello Kristian, hello Alexander,
On 11.03.2016 12:20, Alexander Barkov wrote:
> So we follow the PAD SPACE requirement for default collations here.
I think it's reasonable that the default collations are implemented according
to the standard. Nevertheless, the standard enforces an exceptionally
Hi,
I just released the latest version of my replication manager utility for
MariaDB. It has some tremendous improvements over the last version, so if
you are using it please upgrade, or check it out at
https://github.com/mariadb-corporation/replication-manager
Main features:
- Agentless utility
> Le 11 Mar 2016 à 14:39, Binarus a écrit :
>
> On 11.03.2016 12:59, rhys.campb...@swisscom.com wrote:
>> I think I could try this as a last resort, but it would require changes in
>> the existing applications.
>>
>> Could do it with a trigger to avoid application changes although that's
>>
FYI, I have added a new task for this:
https://jira.mariadb.org/browse/MDEV-9711
On 03/11/2016 03:20 PM, Alexander Barkov wrote:
> Hello Binarus, Kristian,
>
> On 03/11/2016 02:25 PM, Kristian Nielsen wrote:
>> Binarus writes:
>>
>>> "All MySQL collations are of type PADSPACE. This means that
Hello,
A new question has been asked in "What is in the Different MariaDB Releases?"
by p...@mindkicks.com. Please answer it at
http://mariadb.com/kb/en/will-mariadb-add-json-components-like-mysql-recently-announced/
as the person asking the question may not be subscribed to the mailing list.
On 11.03.2016 13:06, Peter Laursen wrote:
> An idea that may work for you could be to TRIM() -
> http://dev.mysql.com/doc/refman/5.7/en/string-functions.html#function_trim -
> the original varchar column into a virtual (PERSISTENT) column, and add an
> index on this column?
>
I'm not sure if I
On 11.03.2016 12:59, rhys.campb...@swisscom.com wrote:
> I think I could try this as a last resort, but it would require changes in
> the existing applications.
>
> Could do it with a trigger to avoid application changes although that's
> something I'd probably try to avoid.
Agreed. I want to a
An idea that may work for you could be to TRIM() -
http://dev.mysql.com/doc/refman/5.7/en/string-functions.html#function_trim
- the original varchar column into a virtual (PERSISTENT) column, and add
an index on this column?
Peter
On Fri, Mar 11, 2016 at 12:59 PM, wrote:
> I think I could try
I think I could try this as a last resort, but it would require changes in the
existing applications.
Could do it with a trigger to avoid application changes although that's
something I'd probably try to avoid.
If you can afford it, then you could only index part of your VRAHCAR columns to
mak
Hello Binarus, Kristian,
On 03/11/2016 02:25 PM, Kristian Nielsen wrote:
> Binarus writes:
>
>> "All MySQL collations are of type PADSPACE. This means that all CHAR,
>> VARCHAR, and TEXT values in MySQL are compared without regard to any
>> trailing spaces. “Comparison” in this context does not
On 11.03.2016 10:56, rhys.campb...@swisscom.com wrote:
> Just a quick idea... Perhaps you can include an additional field in the
> unique index containing the length on the string. So
>
> Str, str_len
> 'a', 1
> 'a ', 2
>
> Unq index on (str, str_len).
>
Thanks for the suggestion. I already
Binarus writes:
> "All MySQL collations are of type PADSPACE. This means that all CHAR,
> VARCHAR, and TEXT values in MySQL are compared without regard to any
> trailing spaces. “Comparison” in this context does not include the
Yes, I have always found this terminally stupid as well. But I think
On 11.03.2016 10:30, Reindl Harald wrote:
> Am 11.03.2016 um 09:19 schrieb Binarus:
>> To make a long story short: I would like to have CHAR and VARCHAR fields
>> with unique indexes which consider 'a' and 'a ' to be different values
>> (which is the only reasonable point of view IMHO). This is n
Just a quick idea... Perhaps you can include an additional field in the unique
index containing the length on the string. So
Str,str_len
'a',1
'a ', 2
Unq index on (str, str_len).
Rhys
-Original Message-
From: Maria-discuss
[mailto:maria-discuss-bounces+rhys.campbell=swissc
Am 11.03.2016 um 09:19 schrieb Binarus:
To make a long story short: I would like to have CHAR and VARCHAR fields with
unique indexes which consider 'a' and 'a ' to be different values (which is the
only reasonable point of view IMHO). This is not possible with MySQL. Is it
possible with Mari
Dear all,
I already have done some MySQL development and now eventually would like to
switch to MariaDB because I no longer can stand the following:
"All MySQL collations are of type PADSPACE. This means that all CHAR, VARCHAR,
and TEXT values in MySQL are compared without regard to any trailin
21 matches
Mail list logo
