yes, there was a bug around that, now I remember.
and probably the version for Pharo 4 does not have the fix… I do not remember
exactly where was the problem, let me review a bit...
Esteban
> On 22 Feb 2017, at 14:51, Hilaire <hila...@drgeo.eu> wrote:
>
> I though String may be problematic, so I try with Association.
> The problem still occurs at,
> self collectionAt: anObject class inDatabase: db
>
> There I can see at least a command failed error.
> The collection can't be added.
>
> In addCollection: aString capped: aCapped size: aSize max: aMax, the
> reply from DB is:
>
> a Dictionary('code'->15888 'errmsg'->'exception: must pass name of
> collection to create' 'ok'->0.0 )
>
> Le 22/02/2017 à 14:40, Esteban Lorenzano a écrit :
>> no, but String probably will be complicated to persist “as is” (is not
>> directly mappeable to a JSON/BSON object). Better to test with another
>> object (like your original post).
>> we need to see what is the error you’re getting… the loop seems to be
>> happening in a resignalAs: so there is an error somewhere (not that is good
>> it resignal it instead showing it, but let’s go in parts :P)
>>
>> Esteban
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
