Aha ok so the file grew by accident to become something that is not really
best practice?
Anyway your template example pointed the way for me, I simply "pad" my dbs
E/R like so:
(dbs
(3 +Page #1
+PageAttr
+Block
+BlockAttr
+Menu
+MenuAttr
+AclGroup
+AclPerm
+AclUserLink
+AclPermLink
+Lang
+LocStr
+LocCache
+Sess )
(4 +User) #2
(4 (+User id username)) #3
(3 (+Page id name path parent) #4
(+Block id page type name loc parent)
(+BlockAttr id block name value)
(+PageAttr id page name value)
(+Menu id name parent page pos)
(+MenuAttr id menu name value)
(+AclGroup id name)
(+AclPerm id name)
(+AclUserLink id user acl)
(+AclPermLink id perm acl) )
(4 (+LocStr id name lang val reqTime) #5
(+LocCache id page str)
(+Lang id lang))
(4 (+Sess id user sid data exp) ) #6
(3) #7
(4) #8
(5) #9
(6) #10
(3) #11
(4) #12
(5) #13
(6)) #14
And then in the project building on the framework:
(dbs+ 15
(3 +Blog)
(3 (+Blog id url hline content pdate)) )
I have tested to later add something in for instance file #7.
Works.
On Mon, Sep 9, 2013 at 2:34 AM, Alexander Burger <[email protected]>wrote:
> Hi Henrik,
>
> > So you recommend 10 files in total, at the begining, no need for more, it
> > might even be suboptimal with more, yet at the end your example has a lot
> > more files than 10.
> >
> > I'm confused?
>
> Sorry, my mail was a bit contradictory.
>
> What I meant is that I usually start with the short one. I always use it
> for a template for new projects. In the initial phase, when the database
> is still changing a lot, this number may increase a bit, but I delete
> and recreate the DB all the time anyway (populating it from a file
> usually called "xxx/init.l").
>
> The long example I posted to show you that you don't need to put a
> single entity or a single index into a single file. The history of
> _that_ 'dbs' call is different, it is from an application running since
> 2001 which was extended and re-organized several times meanwhile (the
> first version was even in the old single-file style of PicoLisp).
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
>
