On Mon, Sep 21, 2020 at 3:05 AM jkn <[email protected]> wrote: Interesting stuff, thanks for this. I shall have to read more about the > 'Associative Model of Data'. >
That might be fun. I took a quick look years ago. However, there is no great need to do so. Speed's insight is that using Leo as a DB is a *whole lot* easier than doing a "real" DB. No need for all the "abilities" (Reliability, Availability, Serviceability, Serviceability, Scalability, etc) that a real DB must obsess over. Just back up your .leo file one in a while :-) Couple of quick corrections etc. on the posting: > > 1) you have two definitions for 'USE MyDatabase' in the section > "leo_database.py handles SQL queries' > Thanks. Just at present I am not able to edit the post. > 2a) so does each 'table' node necessarily have exactly three children? > Would be worth saying so is so > I don't know for sure. Presumably, that depends on Speed's scripts. I might have used another way, say with @meta, @column and @contents nodes. 2b) Does the Child1 metadata consist only of information as to whether the > Child3 body is data, or a link? If so, would be worth saying. > Again, I don't know. Again presumably, the answer is that the data is similar to whatever the "standard" way describing DB's is. I don't know what that standard way is, but Speed said there is such a way, and it uses 3-tuples. Speed is still looking for the missing scripts. I hope he can find them. The scripts contain the implicit answers to your questions. If Speed can't find them, I think a project to recreate them would be in order. We can then choose for ourselves how we answer your questions. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3xdriWUJTsUrwtiQMdHQ96zPbr%3D5pU84OrdUj%3DrLs2DA%40mail.gmail.com.
