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=20user can simply define these relationships the first time=20it is used, and at any other time he feels like it. Then=20the key fields and relationships (and other operating=20parameters) can be stored in a toolprefs.db file for use=20again 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=20think I called it Ken's DB Admin. It did everything you=20mentioned here and more -- including moving fields around=20into different positions so you could change the field=20order dynamically any time you felt like it ... :)But I used cookies to store the control parameters instead=20of storing them in a separate preference file, and later I=20learned that cookies aren't the best way to store this=20data. Somehow they created an unusual situation where a=20user would have to delete them to continue using the tool. =20I never figured out why this happens but if I were to=20rebuild it I would most definitely use a prefs file. But=20back in the 90's I was determined to make this tool a "one=20file" solution so I used cookies to avoid the need for any=20additional files. =20=2D-----------------------There's an important issue here that makes this kind of a=20tool dangerous to use in some situations too unless you're=20aware of it. I only learned this after I had finished=20coding my db admin tool:When a db contains encrypted data you cannot edit that field=20without screwing up that record or possibly trashing the=20entire db. So if you use this kind of webdna tool you must=20limit its editing use to only those fields that contain=20non-encrypted data.Naturally the tool could be built to disable editing of=20encrypted fields, but it cannot figure out which fields are=20encrypted all by itself, so this is an important setting=20the user must make in the prefs before the tool will=20function properly -- just like setting the name of=20the "sku" field in each db so it knows which field contains=20a 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=20user can simply define these relationships the first time=20it is used, and at any other time he feels like it. Then=20the key fields and relationships (and other operating=20parameters) can be stored in a toolprefs.db file for use=20again 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=20think I called it Ken's DB Admin. It did everything you=20mentioned here and more -- including moving fields around=20into different positions so you could change the field=20order dynamically any time you felt like it ... :)But I used cookies to store the control parameters instead=20of storing them in a separate preference file, and later I=20learned that cookies aren't the best way to store this=20data. Somehow they created an unusual situation where a=20user would have to delete them to continue using the tool. =20I never figured out why this happens but if I were to=20rebuild it I would most definitely use a prefs file. But=20back in the 90's I was determined to make this tool a "one=20file" solution so I used cookies to avoid the need for any=20additional files. =20=2D-----------------------There's an important issue here that makes this kind of a=20tool dangerous to use in some situations too unless you're=20aware of it. I only learned this after I had finished=20coding my db admin tool:When a db contains encrypted data you cannot edit that field=20without screwing up that record or possibly trashing the=20entire db. So if you use this kind of webdna tool you must=20limit its editing use to only those fields that contain=20non-encrypted data.Naturally the tool could be built to disable editing of=20encrypted fields, but it cannot figure out which fields are=20encrypted all by itself, so this is an important setting=20the user must make in the prefs before the tool will=20function properly -- just like setting the name of=20the "sku" field in each db so it knows which field contains=20a 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:
Updating Prices in Online Database (1999)
Signal Raised (1997)
Converting characters to numbers ... (1997)
HELLO (2000)
Date search - yes or no (1997)
[WebDNA] WebDNA 7 (2011)
Grant, please help me ... (1997)
webmerch and serials - almost there (1997)
Moment of Thanks (1997)
Loops in increments of .25 (2002)
How to Display text in empty fields (1997)
Dates (1998)
WebCatalog2 Feature Feedback (1996)
Goodbyes (2007)
woops - speed results - right subject (2002)
Nesting format tags (1997)
Admin Edit prob. (1997)
Extracting URL (2007)
find with exceptions (1997)
Next X hits (1996)