Thanks for the suggestion Scott, I think it's enough indeed, done at revision: 1755390
> It's demo data, what's wrong with it using the demo reader? Any number of
> issues can arise when you modify demo data in the database and then reload
> it. e.g. shipping a demo order and then reloading the XML would leave the
> shipment and issuances in place but revert the order to approved.
>
> Perhaps it should be renamed to PasswordSecurityDemoData.xml
>
> Regards
> Scott
>
> On 6 August 2016 at 02:04, Jacques Le Roux <
[hidden email]>
> wrote:
>
>> Mmm, yes you are right, it can't be seed-initial. But also not ext-demo,
>> it's only for adopters. I finally think we should keep as is or introduce
>> another specialised reader, not a big deal and not for today...
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
>> Le 05/08/2016 à 15:54, Taher Alkhateeb a écrit :
>>
>>> I think by convention seed-initial does not setup users or passwords, that
>>> should be either demo or ext-demo or something like that. Not entirely
>>> sure
>>> of this though.
>>>
>>> On Aug 5, 2016 1:37 PM, "Jacques Le Roux" <
[hidden email]>
>>> wrote:
>>>
>>> Hi,
>>>> I stumbled upon this by chance
>>>>
>>>> <!-- NOTE: comment this line out to ensure no resetting of passwords
>>>> -->
>>>> <entity-resource type="data" reader-name="demo" loader="main"
>>>> location="data/PasswordSecurityData.xml"/>
>>>> <entity-resource type="data" reader-name="demo" loader="main"
>>>> location="data/SecurityGroupDemoData.xml"/>
>>>> <entity-resource type="data" reader-name="demo" loader="main"
>>>> location="data/SecurityTypeDemoData.xml"/>
>>>>
>>>> Should we not use seed-initial rather than demo here?
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
Locked
