The problem with setting MySQL to the old password format is that other
applications (I'm thinking perl / php) might be expecting the new and
improved format. I know the portal system I use on my site has a series
of setup scripts I'm not about to tweak -- I'd have to modify every
patch release, too.
I might use RB to code a nice little management system for my server, as
an example, but right now that's not possible. I'm sure there are far
better examples than this -- but you get the point.
If RB is being used to access data created and updated by another
application, then you don't want to be playing with database settings.
This is true of any database server, it just so happens MySQL has the
nastiest little catch in RB with the password issue.
Of course, you could change the MySQL settings at the highest level so
every password is in the old format. I'm not sure if that would affect
the longer passwords generated by the portal I use or not. I think the
password length does change, not just the storage method.
- Scott
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>