Re: [WebDNA] db admin tool

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101469
interpreted = N
texte = --=====================_351441093==.ALT Content-Type: text/plain; charset="us-ascii" I think this is where we're getting off track - you don't need an db admin tool for a flat text file, heck, Excel will manipulate them just fine if you really must. Working with a mySQL db is another story as you have to connect to the datasource, manage tables and schema, etc., and thus a tool like PHPMyAdmin comes in handy as a browser based solution for handling this more complex and dynamic database structuring. At 10:19 AM 11/19/2008, you wrote: >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 --=====================_351441093==.ALT Content-Type: text/html; charset="us-ascii" I think this is where we're getting off track - you don't need an db admin tool for a flat text file, heck, Excel will manipulate them just fine if you really must.

Working with a mySQL db is another story as you have to connect to the datasource, manage tables and schema, etc., and thus a tool like PHPMyAdmin comes in handy as a browser based solution for handling this more complex and dynamic database structuring.

At 10:19 AM 11/19/2008, you wrote:
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
--=====================_351441093==.ALT-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] db admin tool (Kenneth Grome 2008)
  2. Re: [WebDNA] db admin tool (Donovan Brooke 2008)
  3. Re: [WebDNA] db admin tool (Patrick McCormick 2008)
  4. Re: [WebDNA] db admin tool (Patrick McCormick 2008)
  5. Re: [WebDNA] db admin tool ("William DeVaul" 2008)
  6. Re: [WebDNA] db admin tool (Kenneth Grome 2008)
  7. RE: [WebDNA] db admin tool ("Olin Lagon" 2008)
  8. RE: [WebDNA] db admin tool ("Michael A. DeLorenzo" 2008)
  9. Re: [WebDNA] db admin tool (Donovan Brooke 2008)
  10. Re: [WebDNA] db admin tool (Gary Krockover 2008)
  11. [WebDNA] db admin tool (Patrick McCormick 2008)
--=====================_351441093==.ALT Content-Type: text/plain; charset="us-ascii" I think this is where we're getting off track - you don't need an db admin tool for a flat text file, heck, Excel will manipulate them just fine if you really must. Working with a mySQL db is another story as you have to connect to the datasource, manage tables and schema, etc., and thus a tool like PHPMyAdmin comes in handy as a browser based solution for handling this more complex and dynamic database structuring. At 10:19 AM 11/19/2008, you wrote: >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 --=====================_351441093==.ALT Content-Type: text/html; charset="us-ascii" I think this is where we're getting off track - you don't need an db admin tool for a flat text file, heck, Excel will manipulate them just fine if you really must.

Working with a mySQL db is another story as you have to connect to the datasource, manage tables and schema, etc., and thus a tool like PHPMyAdmin comes in handy as a browser based solution for handling this more complex and dynamic database structuring.

At 10:19 AM 11/19/2008, you wrote:
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
--=====================_351441093==.ALT-- Gary Krockover

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

strange math (2004) WebCat2: Found Items syntax, etc. (1997) [OT] 'Email this story to a friend' (2003) trouble updating records in database (1998) How can I Add several Items into the cart at once? (1997) Searching/sorting dates (1997) Listserver problem (1997) New to WebCat-very unsure (2000) WebCat2: multiple currency support (1997) [OT] (waaaay OT) (2004) Hideif not working? (2001) [WebDNA] [store] and [recall]: default db location (2015) Some Questions (1997) form data submission gets truncated (1997) OT - SMSI complaint (2001) Newbie search question (between two dates) (2001) OT-JS why it does not run on Mac (2001) [taxRate] [TaxTotal] ? (1997) Cancel Subscription (1996) RE: [WebDNA] [OT] Phone solution for multiple companies at same location (2010)