> Any objection if I rework this function to meet SQL92 and fix the bug?
I don't object. > Or is the SQL92 part not desirable because it breaks backward > compatability? I don't think so. > In any case, can the #ifdef MULTIBYTE's be removed now in favor of a > test for encoding max length? Sure. -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
