On 9/1/07, Chris Travers <..hidden..> wrote:
Hi;
I appologize for the delay :-)
No problem. I was setting up a 'proof of concept' configuration for what could be a future reference site. I had to take them back to sl for now. :-(. I think there is only my cpan modules issue to sort out , and I can move them back to lsmb fairly easily now. See next.
On 8/26/07,
David Tangye <..hidden..> wrote:
Hi Chris,
A few thoughts and queries now that I have lsmb up and running, with accounts converted from sl.
1. I wrote a script to convert sl datasets: via dump, drop dataset, recreate and run the sl 2.6.12 to
2.6.19 upgrade sql scripts.
Sure. Would be glad to check it out.
See above. Its now a 'forward to lsmb or reverse to sl' script. Its no good now for open release as its too dangerous now, and specific to sl
2.6.12db and lsmb 1.20db (1.2.7) conversions. I shall send you a copy shortly though. I doubt its much use to you though.
3. I see no buttons in the admin facility to upgrade and drop datasets. Have I broken something already :-), or is this removed.
These have been removed :-)
Fine, at least its not me stuffing that part up :-)
4. All my accounts datasets plus the ledgersmb security dataset are now set for utf8 (as were my sl datasets). Do you expect any problem there?
No. THis is the preferred configuration. We support UTF pretty well in 1.2.7.
Yes the lsmb datasets seemed happy with utf8.