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:
Rendering out a page (1997)
name-value pairs (2006)
[WebDNA] products.db (2013)
A little syntax help (1997)
Stopping bad HTML propagation ? (1997)
RE: Upload (1998)
popmenus database and line items (2000)
[WebDNA] Receive JSON POST (2019)
Listfiles & writefile (2001)
[WebDNA] MD5 Hash issue (2009)
Username and password in tcp connect/send (2001)
Remove Command not working (2000)
Re:Emailer and encryption (1997)
Locking up with WebCatalog... (1997)
Emailer (WebCat2) (1997)
New Command prefs ... (1997)
b12 cannot limit records returned and more. (1997)
[HIDEIF] inside [FOUNDITEM] (1997)
HTTP "host" header (2003)
Possible Bug in 2.0b15.acgi (1997)