Re: trouble updating records in database
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19062
interpreted = N
texte = >>Ken Grome: >>The WebDNA programmer, not the software, should perform a check for the >>existence of the duplicate SKU... > At 10:05 Uhr 24.07.1998, Charles Kefauver wrote: >Sure, but it is more work, and the programmer must remember to do so in >each new proyect. In all other Database systems, when you flag a field as >being unique, the underlying database makes sure it is unique. Every >database I have even seen that uses unique fields (and I have seen many) >does this automatically.This is right, but not usable under some circumstances. Most databases are for client/server and not for web. Take 4D for example: if you flag a field as unique then an error message will pop up to warn the user. Fine for a dedicated database client, but if you do not catch this situation in your web-application, the popup would be shown on the webserver! Therefore I agree with Ken - it is more secure when the programmer decides what is unique and what is not. Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21
Associated Messages, from the most recent to the oldest:
>>Ken Grome: >>The WebDNA programmer, not the software, should perform a check for the >>existence of the duplicate SKU... > At 10:05 Uhr 24.07.1998, Charles Kefauver wrote: >Sure, but it is more work, and the programmer must remember to do so in >each new proyect. In all other Database systems, when you flag a field as >being unique, the underlying database makes sure it is unique. Every >database I have even seen that uses unique fields (and I have seen many) >does this automatically.This is right, but not usable under some circumstances. Most databases are for client/server and not for web. Take 4D for example: if you flag a field as unique then an error message will pop up to warn the user. Fine for a dedicated database client, but if you do not catch this situation in your web-application, the popup would be shown on the webserver! Therefore I agree with Ken - it is more secure when the programmer decides what is unique and what is not. Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21
Peter Ostry
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:
Change in Host? (1999)
WebMerchant? (1998)
Close Databases Crash? (1998)
Putting Foundvariables within search. (2000)
Modifying order output (1997)
emailer settings and control questions (1997)
Frames and WebCat (1997)
SKU lookup (1997)
Limiting user access to .tmpl files (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Emailer help....! (1997)
Transfering [text] variables (2000)
Can WC remember people? (1998)
Summing fields (1997)
[group] ? (1997)
RE: Adding headers to email (1997)
Followup question re: checksum for credit cards? (1997)
Apache2 connector (2003)
WebCat2b12--[searchstring] bug (1997)
Frames and WebCat (1997)