[WebDNA] db admin tool
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101468
interpreted = N
texte = --Apple-Mail-4--303750398 Content-Type: multipart/alternative; boundary=Apple-Mail-3--303750455 --Apple-Mail-3--303750455 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit WebDNA uses flat text files, but allows users to build fully relational solutions. It requires that users take responsibility for key fields and maintaining referential integrity, among other things. That usually works well because more formal databases require specification of key fields and relationships at the outset of a project and changing those things can be painful later on. WebDNA allows those things to be changed at any time, which is partly why our development times are reduced. In making an admin tool, this creates some special problems. Because there is no mechanism for structuring key fields and relationships between databases, it would be a huge task to write something that would figure all that out automatically. Without that, an admin tool is nothing more that an interface for looking at what is inside text files. That interface would look like a simple spread sheet and allow addition, modification or deletion of records. Are users looking for an admin tool that can do more? On a side note, I've been looking for a better term than "relational database" Part of WebDNA's unique features is the fact that is uses its own text- based data files, while still allowing the ability to build relational database capabilities. It occurred to me that, because this involves the best of both flat files and relational files, we might consider calling this hybrid "flatulational", but I'm hoping we can come up with a better term. Any ideas? Pat On Nov 19, 2008, at 10:09 AM, Gary Krockover wrote: > Does that connect to MySQL db's as well or just WebDNA flat text db's? > > At 03:49 AM 11/19/2008, you wrote: >> There is the tiny "DB Admin" by Olin, at http://dev.webdna.us/downloads.html >> It is not by far aother "phpMyAdmin" but is very useful to edit >> records. >> >> chris --Apple-Mail-3--303750455 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable WebDNA uses flat text files, = but allows users to build fully relational solutions. It requires that = users take responsibility for key fields and maintaining referential = integrity, among other things.
That usually works = well because more formal databases require specification of key fields = and relationships at the outset of a project and changing those things = can be painful later on. WebDNA allows those things to be changed at any = time, which is partly why our development times are = reduced.
In making an admin tool, this creates = some special problems. Because there is no mechanism for = structuring key fields and relationships between databases, it would be = a huge task to write something that would figure all that out = automatically. Without that, an admin tool is nothing more that an = interface for looking at what is inside text files. That interface = would look like a simple spread sheet and allow addition, modification = or deletion of records.
Are users looking for = an admin tool that can do more?
On a side note, = I've been looking for a better term than "relational = database"
Part of WebDNA's unique = features is the fact that is uses its own text-based data files, while = still allowing the ability to build relational database capabilities. It = occurred to me that, because this involves the best of both flat files = and relational files, we might consider calling this hybrid = "flatulational", but I'm hoping we can come up with a better term. = Any = ideas?
Pat
That usually works = well because more formal databases require specification of key fields = and relationships at the outset of a project and changing those things = can be painful later on. WebDNA allows those things to be changed at any = time, which is partly why our development times are = reduced.
In making an admin tool, this creates = some special problems. Because there is no mechanism for = structuring key fields and relationships between databases, it would be = a huge task to write something that would figure all that out = automatically. Without that, an admin tool is nothing more that an = interface for looking at what is inside text files. That interface = would look like a simple spread sheet and allow addition, modification = or deletion of records.
On a side note, = I've been looking for a better term than "relational = database"
Part of WebDNA's unique = features is the fact that is uses its own text-based data files, while = still allowing the ability to build relational database capabilities. It = occurred to me that, because this involves the best of both flat files = and relational files, we might consider calling this hybrid = "flatulational", but I'm hoping we can come up with a better term. = Any = ideas?