Re: Xaraya Aruba 1.2 roadmap open for comments

Hi all,

my FR would be 
1) to define encoding for database connection - not only because MySQL has still stupidly default encoding as Latin1.
There are several resources about this problem in Xaraya (the best link I just can't find)
http://bugs.xaraya.com/show_bug.cgi?id=2758
http://bugs.xaraya.com/show_bug.cgi?id=6109
http://www.xaraya.com/index.php/xarbb/topic/2589

Basically there would be parametter defined in var/config.system.php:
 $systemConfiguration['DB.Encoding'] = 'encoding_name';
which would be used in query:
 "SET NAMES encoding_name" (don't know if there is better way how to accomplish it with adodb).
in function &xarDBNewConn($args = NULL) defined in includes/xarDB.php 

Next step would be adjusting installer to allow setting this parametter.

I'd skip collation settings as it seems to be more difficult (according to Dracos adodb does NOT support collation).
This would be at least for mysql and postgresql. I have no idea how is encoding used in sqlite.



2) only ASCII characters in Short-URLs
In talks about ASCII characters in Short-URLs in articles I've heard that is has to be defined generally for xaraya.

So, it would be good to have only ASCII characters in Short-URLs.
E.g. In Czech "žlutě" would be "zlute", but "zlute" would be also "zlute".
So is that possible? I mean decoding from short url wouldn't be one way :-( ("zlute" could be "zlute" or "žlutě".) If not, it should be somehow achieved avoiding NON-ASCII characters in Short-URLs.

There is a bug about this issue:
http://bugs.xaraya.com/show_bug.cgi?id=3138



3) test more with PostgreSQL (several problems with MySQL put me off from ideas to switch from MySQL to my favourite PostgreSQL).


Pev