Hey Taco, Just a few comments, and these are definately hypocritical (eg. I work the same way as you do but do wonder sometimes...)
JS validation? good for instant feedback but what if you don't have JS? (again, many of the apps I have assume javascript and don't work without (eg. javascript validation submits the form so no JS = no form submission) This is generally a constraint of time, features and budget - but what do people consider the minimum support for non JS clients? ColdFusion validation? yeah I agree with you Taco, and this is where the bulk of our validation gets done for EXACTLY the reasons you've mentioned (flexibility and built in functions mean that catching errors can be handled in any way you like... and I don't claim to be the greatest coldfusion programmer but there are things I could do in half an hour that would take an experienced programmer with insight into a PARTICULAR RDBMS a day or so, and would still require some sort of cooperation at the presentation level) SQL validation? Well this is where I disagree but do it in the same way as you do anyway because of time. I think MORE should be done in SQL and I think, on the whole, the bottleneck in terms of response time is between the client's browser and the webserver. (meaning an SQL statement here and there is not going to add a whole lot and it's the 'last word' when we're talking data integrity) (Remember these are form submissions and validation etc, not 'just page hits' which should be as light on the database as possible) Anyway - this is becoming off the original topic somewhat but I'd love to know what people think. - James > -----Original Message----- > From: Taco Fleur [mailto:[EMAIL PROTECTED] > Sent: Thursday, 18 March 2004 9:10 AM > To: CFAussie Mailing List > Subject: [cfaussie] Re: Database programming > > > IMHO, data validation should be done by JS on the first > level, on the second > level by CF, if the db would do the validation it would mean a lot of > traffic going back and forth, besides MS SQL does not support Regular > Expressions so data filtering is not that easy. As I said, > there should > still be constraints within the RDBMS. [I know other great RDBMS's do > support regex] > In the end we all have our own ways of doing things, and I > guess they are > good for a particular job, and its all about what your used > to. In my case I > am used to working with a framework that auto generates JS client-side > validation and auto generates CF server-side validation all > controlled by > one simple (meta) structure that describes each form field, > thus in theory > invalid data will never hit my db. I have not written any JS or CF > validation in two years, I only drop my framework, adjust the > structure > which is usually done by a wireframing tool I use. > > Taco Fleur > > Tell me and I will forget > Show me and I will remember > Teach me and I will learn > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of WALTERS Scott > > Sent: Thursday, 18 March 2004 7:43 AM > > To: CFAussie Mailing List > > Subject: [cfaussie] Re: Database programming > > > > > > imho, the DBMS is the protector of data, hence it should be > > validating everything that goes in, and it should perform any > > associated tasks without being asked to do it by the app (eg > > update an article requires incrementing workflow, writing an > > audit record etc) > > > > Basically, multiple apps should be able to hook into the one > > database and use it without having to be aware of potentially > > different validation logic in other apps. That doesn't > > preclude validation logic sitting in the app itself, it just > > means that ultimately data must be validated by the database > > before its acceptable. > > > > Cheers > > > > Scott. > > > > -----Original Message----- > > From: Taco Fleur [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 18 March 2004 07:15 AM > > To: CFAussie Mailing List > > Subject: [cfaussie] Re: Database programming > > > > > I'm really interested in getting the DB to do more work for > > > me, but am just wondering about the best way to approach it... > > > > > > Currently I use the database for very little except storing > > > the data... all the logic and validity checking is done in > > > the application. I know > > > should be using it for more, which is why I'm learning more > > > about it now. > > > > I still suggest to have it to do everything but the validity > > checking, I see that as unneeded traffic to the database. > > > > > > IMPORTANT NOTICE: This e-mail and any attachment to it are > > intended only to be read or used by the named addressee. It > > is confidential and may contain legally privileged > > information. No confidentiality or privilege is waived or > > lost by any mistaken transmission to you. The RTA is not > > responsible for any unauthorised alterations to this e-mail > > or attachment to it. Views expressed in this message are > > those of the individual sender, and are not necessarily the > > views of the RTA. If you receive this e-mail in error, please > > immediately delete it from your system and notify the sender. > > You must not disclose, copy or use any part of this e-mail if > > you are not the intended recipient. > > > > --- > > You are currently subscribed to cfaussie as: > > [EMAIL PROTECTED] To unsubscribe send a blank email to > > [EMAIL PROTECTED] > > > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia > http://www.mxdu.com/ + 24-25 February, 2004 > > > --- > You are currently subscribed to cfaussie as: > [EMAIL PROTECTED] > To unsubscribe send a blank email to > [EMAIL PROTECTED] > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia > http://www.mxdu.com/ + 24-25 February, 2004 > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
