So these changes are done in a dynamic way, maybe through a user interface,
eg add middle name to +User through a form submission in an admin interface
On Wed, Sep 11, 2013 at 09:57:49PM +0700, Henrik Sarvell wrote:
> Some kind of dynamic ALTER TABLE equivalent? In that case won't you need to
> also manipulate the *Dbs data?
>
> Plus modifying the E/R files?
This is not necessary.
The E/R files call 'rel', which is just 'put'ting some informati
What is the practical case you're working with, why do you want to do what
you describe?
Some kind of dynamic ALTER TABLE equivalent? In that case won't you need to
also manipulate the *Dbs data?
Plus modifying the E/R files?
On Wed, Sep 11, 2013 at 7:29 PM, Thorsten Jolitz wrote:
> Alexande
On Wed, Sep 11, 2013 at 02:29:21PM +0200, Thorsten Jolitz wrote:
> So, as a conclusion, external objects (entities) are not as dynamically
> extendable as normal objects because of the need to keep the DB intact.
True.
> If I want (at runtime) other or more relations than defined for the
> origi
Alexander Burger writes:
> On Wed, Sep 11, 2013 at 01:47:01PM +0200, Thorsten Jolitz wrote:
>> Ok, one question remains (back to the original topic of this thread, so
>> to say):
>
> Right :)
>
>> ,--
>> | (class +MyClass +Entitiy)
>> | (rel :friend (+String))
>> | (rel :b
On Wed, Sep 11, 2013 at 01:47:01PM +0200, Thorsten Jolitz wrote:
> Ok, one question remains (back to the original topic of this thread, so
> to say):
Right :)
> ,--
> | (class +MyClass +Entitiy)
> | (rel :friend (+String))
> | (rel :birth (+Date))
> `-
Alexander Burger writes:
> On Wed, Sep 11, 2013 at 12:42:24PM +0200, Thorsten Jolitz wrote:
>> Thanks, then I will just map over my property list and assign them "the
>> canonical way" with 'put>' and friends.
>
> Or, if you have (or convert) the property list in a form like
>
>(key1 val1 key
Alexander Burger writes:
> On Wed, Sep 11, 2013 at 12:42:24PM +0200, Thorsten Jolitz wrote:
>> Thanks, then I will just map over my property list and assign them "the
>> canonical way" with 'put>' and friends.
>
> Or, if you have (or convert) the property list in a form like
>
>(key1 val1 key
On Wed, Sep 11, 2013 at 12:42:24PM +0200, Thorsten Jolitz wrote:
> Thanks, then I will just map over my property list and assign them "the
> canonical way" with 'put>' and friends.
Or, if you have (or convert) the property list in a form like
(key1 val1 key2 val2 ..)
you might as well use 'ne
Alexander Burger writes:
Hi Alex,
> Therefore, a property of an '+Entity' should always be assigned using
> 'put>' and related methods. These methods take care of maintaining all
> side effects necessary for DB consistency.
[...]
> However, I would recommend always to use 'put>', because it av
Hi Thorsten,
> a very nice feature of the PicoLisp object system is the ability to add
> new attributes at runtime (add new properties to the symbols property
> list), e.g. create an object with 5 attributes although the class only
> expects 2 attributes.
Correct.
> But what about external symb
Hi List,
a very nice feature of the PicoLisp object system is the ability to add
new attributes at runtime (add new properties to the symbols property
list), e.g. create an object with 5 attributes although the class only
expects 2 attributes.
But what about external symbols (entities)?
If some
12 matches
Mail list logo
