>
> Thank you very much for this explanation.
>
> Regarding the version: Our O/S usually is Debian which generally uses
> software which is quite old. This means that I will have to compile MariaDB
> myself in every case. The current project where this new collations are
> needed will probably
e grateful for any progress regardless of the order of things being
implemented.
Binarus
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
Should we continue our conversation on the developer mailing list?
Regards,
Binarus
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : http
ke to have
these, too?
Regards,
Binarus
>
> 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 typ
> 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
>
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
x27;s worthy to implement
> at least utf8_nopad_bin and utf8_unicode_nopad_ci at once,
> and then eventually NO PAD collations for all other character sets.
Personally, I would be totally happy if I had the three new utf8 collations (I
probably will never use anything else than utf8 for string
I'm not sure if I understand you correctly, but using TRIM() on that column
would make the value 'a' the same as the value 'a ' which is exactly how
MariaDB's indexes already work by default and the thing which I would like to
avoid. Have
respective rows in all tables from VARCHAR(255) to VARBINARY(765).
Thank you very much again,
Binarus
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
ond column to the same index at all?
If I have to go this way as a last resort, I'll investigate ...
Binarus
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : http
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 onl
so, I
would like to know if there is an easy, clean solution).
Thank you very much for any ideas,
Binarus
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
12 matches
Mail list logo
