Re: EDB and multi-value databases.
Once you "THINK" PICK like, it is very hard to go back to, what I call
normal views for data.
The AppGen experience PROVIDES something very lacking in LINUX,
a VERY RAPID and easy development platform.
A GOOD part of that power comes from the MV database usage itself.
Screens and reports are done via a WYSIWYG generator, with
breakouts to various points in each "field" manipulation. More
like a VERY high level IDE that enforces a strict structure of
both syntax and verbiage. Even thought this is done with a "green"
screen approach, the "PDEFS" (Procedure Definitions), are IN FACT,
really stored presentation agnostic.
What you gain from that, is the runtime provides ALL of the
mundane tasks, such as file i/o, function key mapping,
presentation management (i.e. - Green screen or Graphics).
The APPGEN runtime, in is simplest definition, is JUST
5 modules - Menu, Maint (screens), Selectem/Sortem (displays
the "AQL" - really a restricted set and the mother of SQL -
that creates the "on the fly" AQL statements), Printem (reports),
Postem (Batch updating).
All of the PDEFS, themselves, are a MV file.
The problem lies in the fact, that if UniVerse/UniData, MVbase,
RELATIONAL, PICK (And other current MV DBM's) could be called
"fourth generation" iterations, Appgen's PICK implementation is
stuck at "second generation".
Derek Parnell wrote:
>
>
> I've worked a bit with Pick-like databases and can see their uses.
>The EDB system from RDS can already take advantage of a
>multi-value idea. For example, a traditional Relational DBMS
>would typically have a table for Orders and another table
>for OrderLines and yet another for Receipts. But using EDB,
>you would naturally combine these into a single
>table - thanks to Euphoria's sequences.
>
--
Ben Duncan Phone (601)-355-2574 Fax (601)-355-2573 Cell (601)-946-1220
Business Network Solutions
336 Elton Road Jackson MS, 39212
"Software is like Sex, it is better when it's free" - Linus Torvalds
|
Not Categorized, Please Help
|
|
