Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/07/2010 12:52 AM, David O'Brien wrote:
>> Simo Sorce wrote:
>>> Now the upgrade process can cope with converting ols ssd.ldb files into
>>> multiple databases even if the new config file does not include a
>>> "lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2010 12:52 AM, David O'Brien wrote:
> Simo Sorce wrote:
>> Now the upgrade process can cope with converting ols ssd.ldb files into
>> multiple databases even if the new config file does not include a
>> "local" provider anymore.
>>
>> Tested w
Simo Sorce wrote:
> Now the upgrade process can cope with converting ols ssd.ldb files into
> multiple databases even if the new config file does not include a
> "local" provider anymore.
>
> Tested with a v1 db file and seem to work fine with and w/o a LOCAL
> provider defined in the configuratio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2009 07:22 AM, Sumit Bose wrote:
> On Mon, Dec 14, 2009 at 04:03:27PM -0500, Simo Sorce wrote:
>> Now the upgrade process can cope with converting ols ssd.ldb files into
>> multiple databases even if the new config file does not include a
>> "
On Mon, Dec 14, 2009 at 04:03:27PM -0500, Simo Sorce wrote:
> Now the upgrade process can cope with converting ols ssd.ldb files into
> multiple databases even if the new config file does not include a
> "local" provider anymore.
>
> Tested with a v1 db file and seem to work fine with and w/o a LO
Now the upgrade process can cope with converting ols ssd.ldb files into
multiple databases even if the new config file does not include a
"local" provider anymore.
Tested with a v1 db file and seem to work fine with and w/o a LOCAL
provider defined in the configuration.
Simo.
--
Simo Sorce * Re
