Re: [WebDNA] db admin tool
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101475
interpreted = N
texte = > 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. The tool doesn't have to figure it out automatically, the=20 user can simply define these relationships the first time=20 it is used, and at any other time he feels like it. Then=20 the key fields and relationships (and other operating=20 parameters) can be stored in a toolprefs.db file for use=20 again later. > I actually started building a modern, ajax driven db > admin tool that is much more powerful than the one built > in the 90s. Essentially it does everything you need =E2=80=93 > create a db, edit a db, remove fields, add fields, add > records, remove records, edit records, search, delete db, > backup dbs, restore dbs, etc. I did this many years ago too (not in ajax though) and I=20 think I called it Ken's DB Admin. It did everything you=20 mentioned here and more -- including moving fields around=20 into different positions so you could change the field=20 order dynamically any time you felt like it ... :) But I used cookies to store the control parameters instead=20 of storing them in a separate preference file, and later I=20 learned that cookies aren't the best way to store this=20 data. Somehow they created an unusual situation where a=20 user would have to delete them to continue using the tool. =20 I never figured out why this happens but if I were to=20 rebuild it I would most definitely use a prefs file. But=20 back in the 90's I was determined to make this tool a "one=20 file" solution so I used cookies to avoid the need for any=20 additional files. =20 =2D----------------------- There's an important issue here that makes this kind of a=20 tool dangerous to use in some situations too unless you're=20 aware of it. I only learned this after I had finished=20 coding my db admin tool: When a db contains encrypted data you cannot edit that field=20 without screwing up that record or possibly trashing the=20 entire db. So if you use this kind of webdna tool you must=20 limit its editing use to only those fields that contain=20 non-encrypted data. Naturally the tool could be built to disable editing of=20 encrypted fields, but it cannot figure out which fields are=20 encrypted all by itself, so this is an important setting=20 the user must make in the prefs before the tool will=20 function properly -- just like setting the name of=20 the "sku" field in each db so it knows which field contains=20 a unique value in each record. Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
> 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. The tool doesn't have to figure it out automatically, the=20 user can simply define these relationships the first time=20 it is used, and at any other time he feels like it. Then=20 the key fields and relationships (and other operating=20 parameters) can be stored in a toolprefs.db file for use=20 again later. > I actually started building a modern, ajax driven db > admin tool that is much more powerful than the one built > in the 90s. Essentially it does everything you need =E2=80=93 > create a db, edit a db, remove fields, add fields, add > records, remove records, edit records, search, delete db, > backup dbs, restore dbs, etc. I did this many years ago too (not in ajax though) and I=20 think I called it Ken's DB Admin. It did everything you=20 mentioned here and more -- including moving fields around=20 into different positions so you could change the field=20 order dynamically any time you felt like it ... :) But I used cookies to store the control parameters instead=20 of storing them in a separate preference file, and later I=20 learned that cookies aren't the best way to store this=20 data. Somehow they created an unusual situation where a=20 user would have to delete them to continue using the tool. =20 I never figured out why this happens but if I were to=20 rebuild it I would most definitely use a prefs file. But=20 back in the 90's I was determined to make this tool a "one=20 file" solution so I used cookies to avoid the need for any=20 additional files. =20 =2D----------------------- There's an important issue here that makes this kind of a=20 tool dangerous to use in some situations too unless you're=20 aware of it. I only learned this after I had finished=20 coding my db admin tool: When a db contains encrypted data you cannot edit that field=20 without screwing up that record or possibly trashing the=20 entire db. So if you use this kind of webdna tool you must=20 limit its editing use to only those fields that contain=20 non-encrypted data. Naturally the tool could be built to disable editing of=20 encrypted fields, but it cannot figure out which fields are=20 encrypted all by itself, so this is an important setting=20 the user must make in the prefs before the tool will=20 function properly -- just like setting the name of=20 the "sku" field in each db so it knows which field contains=20 a unique value in each record. Sincerely, Ken Grome
Kenneth Grome
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:
[Sum] function? (1997)
categorys (1998)
Protect (1997)
Server Freeze (1998)
Error Lob.db records error message not name (1997)
Looking up two prices in database? (1997)
Blocking off access (2005)
Showif, Hideif reverse logic ? (1997)
[WebDNA] Finding duplicate emails in a large database (2016)
SSL and Webcat (2000)
Size limit for tmpl editor ? (1997)
InSecureTextVariables.... (2000)
Using Plug-In while running 1.6.1 (1997)
[addlineitems] display (1997)
RE: completed orders database (1997)
detecting if var is blank? (2007)
Listwords and the & (2001)
3RD POST Character limit in [Search]? (1998)
Sendmail and textarea (1998)
Summing Fields (1998)