Re: Database Input Validation

2015-07-10 Thread Bob Sneidar
IMHO, there are times when validating on closeField is useful, but if it is the only way you validate, it can also be a frustration to the end user. Lets say the user enters the name in an email address, but forgets what the domain part is. He goes to navigate to his email program, and Livecode

Re: Database Input Validation

2015-07-08 Thread Pascal Lehner
Hi Peter Thanks for the link, your webinar stuff does provide some valuable information :-) I saw your work on SQLMagic.. is there any ETA? Best, Pascal 2015-07-07 18:24 GMT+02:00 Peter Haworth : > Hi Pascal, > Sounds like I may have misunderstood your original question. > > I'm a firm believe

Re: Database Input Validation

2015-07-07 Thread Peter Haworth
Hi Pascal, Sounds like I may have misunderstood your original question. I'm a firm believer in putting data validation functionality into your database schema. There are several SQL DDL features that allow you to do that and several advantages to having the database handle it for you instead of w

Re: Database Input Validation

2015-07-07 Thread Pascal Lehner
Hi Peter and Bob, Thanks for your ideas. I think I found a good way by doing a input check for the user fields on closeField to avoid totally wrong information and then I will store this unicode encoded in the database. This should avoid quite a few problems from the start. Regards, Pascal 2015-

Re: Database Input Validation

2015-07-06 Thread Peter Haworth
Hi Pascal, I assume you're referring to SQL injection attacks. You can avoid them by using the varslist/arrayname parameter of revDataFromQuery/revQueryDatabase/revExecute SQL. See the dictionary for more details but it involves using placeholders in your SQL statements and loading the values for

Re: Database Input Validation

2015-07-06 Thread Bob Sneidar
Sorry try/catch is not a loop. :-) Bob S > On Jul 6, 2015, at 13:12 , Bob Sneidar wrote: > > One way I used in the past was to get the schema of the table, and for each > column I would be updating I would check type, length, limits etc. to make > sure my data fell within the constraints of

Re: Database Input Validation

2015-07-06 Thread Bob Sneidar
One way I used in the past was to get the schema of the table, and for each column I would be updating I would check type, length, limits etc. to make sure my data fell within the constraints of the column. Another way involves using the error messages SQL sends back when a query fails to determ

Database Input Validation

2015-07-06 Thread Pascal Lehner
Hi all, I am working on a desktop app that is running a SQLite database and might well end up as a HTML5 server version with MySQL in the not-so-far future. For this I want to have some sort of input validation to avoid security and XSS incidents. Does anyone have a library or function to "saniti