Hi Jorge, You wrote: >I don't know how the database enconding could damage your other products. > >if you may, could you tell which they are?
:-) The whole thing is a little week-end project. I've been fiddling with it on and off, and over the years I've tried pretty much every web development thing I've laid my hands on. It's not really a "product" in any traditional sense; it's more my personal playground for learning web stuff. Currently, it's a bunch of scripts in various languages, some of it Java, some XSLT, etc. As said previously, I plan to move it all over to Python & TurboGears eventually. I'm not really sure if or how much damage a change in the DB structures (or column types) will cause. It's just that I'd have to review & work through all the old code first, so I'd have results with TurboGears only in a few weeks, rather than now... and getting results immediatly is what attracted me to TurboGears in the first place... :-P >they may not depend on iso-8859-, just happen to be created that way then >you may *fix* that problem. > [...] >Even if it's more work it's better to correct the error then to work around >it :) I think you are basically right. However, I do not think storing iso-8859-1 could be considered an 'error' by itself. Maybe not optimal, but not really wrong either. Also, I think I've solved the problem now; I'll post that in a seperate mail. Thanks, Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
