SQLite, many of us are once again cut out of the loop. That the
structural changes require a deep understanding of the 'new engine' to
make the missing extensions available cuts out other people picking up
the baton easily, so we are stuck with a half built alternative and no
roadmap as to when it may be testable by everyone?
The 32/64 bit discussion has a great relevance to interfaces like the
database ones where these may already be supporting 64bit length
strings, and the like, so coming up with an acceptable compromise on
this is important.
I STILL see 'unicode' in this jigsaw as maintaining 32bit length strings
with a multibyte capability for those areas where in reality even a
16bit limit would be more appropriate? Can we please identify all of the
elements that need to be addressed for PHPNext, rather than pushing
votes on things which essentially combine a number of unrelated options.
PHP still has to support 32bit lengths on 32bit platforms so 64bit
strings have to co-exist with that.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk