2005/12/18, John Siracusa wrote: [..snip..] > > However it is mastery to me why both automations don't work using > > auto_initalize in my R:D:O object? It works fine when I manually > > specify the columns/keys/relations (or copy/pasting the output of > > perl_class_definition in the module). Any ideas? > > What version of RDBO are you using? This sounds like I bug that I fixed a > few versions ago, but maybe it's back (or maybe I didn't fix it completely). > If you can send me a small, self-contained test case that fails on the > latest RDBO (0.58 right now) I'll be sure to fix it in the next release.
I sent directly to John a test case how to reporoduce the problem. [..snip..] > > The described new features above fit perfectly with my needs! However, > > I'm not sure they should be in core RDBO distro since the whole UTF8 > > adventure roots in the lack of UTF8 support in DBD::mysql. I think > > they should be in separate CPAN distro managing with UTF8 > > incompatibilities. > > > > BTW, does someone has similar problems with Postgre/SQLite? > > Encoding is a bit of a hassle everywhere. Even when the DBD seems to do the > right thing, its definition of "right" doesn't always agree with everyone. > I'd like RDBO to be able to handle most common needs. Being in the core > doesn't mean it'd be used by default, just that it's available upon request. > It wouldn't affect anyone who doesn't explicitly ask to use it. That's OK with me - adding a built-in option for encoding/decoding will be nice feature to have. Later on, I can migrate my custom code to the one in the framework. > >> Anyone have any suggestions for better approaches to this problem? Is > >> there > >> an even more generic way to handle encoding/decoding? Should these checks > >> and operations be done on load only or on set as well? > > > > I lean toward the trigger approach done on inflate because (as stated > > above): > > (a) it is execute on demand > > (b) converts any broken octets which aren't supposed to be in a > > full-blown UTF8 app. > > As I said before, (a) will be true of the built-in solution as well. I'm > inclined to make the built-in solution do (b) as well, just to be safe. This is great - would you consider adding it in the upcoming versions? Regards, Svilen ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
