>From RIFE perspective there's nothing that should causing any problems when you do that. Actually, I recommend all databases that RIFE works with to use UNICODE as the storage format, unless there's a really good reason to not do so (space saving for instance).
I'd say, go for it! On 5/30/07, David HM Spector <[EMAIL PROTECTED]> wrote: > > > Once Again, Microsoft's non-adherence to standards bites an innocent > by-stander. It seems that even when told to export outlook contacts as > ASCII, > MS insists on putting "smart quote" crud into ASCII files. > > Postgres, in my case, tries to translate it into a LATIN-1 char and dies > horribly on the row insert... > > my question is: Is there any harm from a RIFE perspective of dumping > the DB, creating a new DB who default charset is UNICODE and then > re-importing the data and then continuing with the entire DB multi-script > capable..? > > David > > > -- > > -------------------------------------------------------------------------------- > David HM Spector > [EMAIL PROTECTED] > voice: +1 631.261.5013 > http://www.zeitgeist.com/ > > "New and stirring things are belittled because if they are not belittled, > the humiliating question arises, 'Why then are you not taking part in > them?'" > --H. G. > Wells > > > > > > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
