Re: [WebDNA] Wishlist: ignore whitespace in database changes

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112945
interpreted = N
texte = 532 I completely agree on the flexibility of manipulating data in variables. = I love the simplicity of doing silly things like [text]age=3D27[/text] = and then [showif [age]>18]=20 (which strictly speaking shouldn=E2=80=99t be legal since age is a = numeric value in a "text" variable.) If anything the [text] tag should be called [variable] to be more = accurate about what=E2=80=99s being stored in it, i.e. unknown variable = data=E2=80=A6=20 That being said, I completely disagree when it comes to storing and = retrieving information in a data structure. If i have a field in a data = structure (read: SQL data table or WebDNA database) that is for storing = dates, then allowing someone to store "yesterday" is nonsensical and = causes problems when I try to retrieve dates based on a calculation. = (i.e. leMODDATEdata=3D12/31/2015) Of course I should write code that = stops this data from being stored in the first place, but as a last = resort the database program itself should defend the database to protect = the integrity of the data stored in it. The side effect, which almost = outweighs the protection factor to be candid, is that when retrieving = info, if each field has a predefined data type, the database already = knows how to deal with searches so the programmer doesn't have to = reiterate for each search that this field is a date, or a number, or = whatever.=20 Just my two cents.=20 -Brian B. Burton > On Aug 31, 2016, at 2:57 PM, christophe.billiottet@webdna.us wrote: >=20 > I personally believe this extra flexibility allows to deal with = database content the way we want, and allows to treat a single field = either as a date, a number or a text field, or even the tree types in a = single page of code. >=20 > I think extra rigidity diminishes creativity, and what I like most in = WebDNA is that it behave like a "chameleon" language. It is so flexible = that you can do whatever you want with it, the way you want. >=20 > I would be interested to read what others have to say about this = requested modification, >=20 > - chris >=20 >=20 >=20 >=20 >=20 >> On Aug 31, 2016, at 20:08, Brian Burton wrote: >>=20 >> Over the years I=E2=80=99ve been bending WebDNA to my will. I=E2=80=99v= e more or less successfully implemented the view and controller ideology = of an MVC framework in WebDNA, and am getting ever closer to doing the = work to get data models working in webDNA. It=E2=80=99s so frustrating = in 2016 to not be able to tag a field in a database as unique or numeric = and let the language deal with it for you when you interact with the = database. I recently wasted more time then I care to admit to making = [delete db=3Dsomedb&leIDdata=3D10000] work because i forgot to add = &IDtype=3Dnum to the code. >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Stuart Tremain 2016)
  2. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Patrick McCormick 2016)
  3. Was: [WebDNA] Wishlist: ignore whitespace in database changes - Now: WebDNA Data Model (dbrooke@euca.us 2016)
  4. [BULK] Re: [WebDNA] Wishlist: ignore whitespace in database changes (Alex McCombie 2016)
  5. Was: [WebDNA] Wishlist: ignore whitespace in database changes - Now: WebDNA Data Model (dbrooke@euca.us 2016)
  6. Re: [WebDNA] Wishlist: ignore whitespace in database changes (christophe.billiottet@webdna.us 2016)
  7. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Stuart Tremain 2016)
  8. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Brian Burton 2016)
  9. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Kenneth Grome 2016)
  10. Re: [WebDNA] Wishlist: ignore whitespace in database changes (christophe.billiottet@webdna.us 2016)
  11. Re: [WebDNA] Wishlist: ignore whitespace in database changes (Brian Burton 2016)
  12. Re: [WebDNA] Wishlist: ignore whitespace in database changes (dbrooke@euca.us 2016)
  13. [WebDNA] Wishlist: ignore whitespace in database changes (Brian Burton 2016)
532 I completely agree on the flexibility of manipulating data in variables. = I love the simplicity of doing silly things like [text]age=3D27[/text] = and then [showif [age]>18]=20 (which strictly speaking shouldn=E2=80=99t be legal since age is a = numeric value in a "text" variable.) If anything the [text] tag should be called [variable] to be more = accurate about what=E2=80=99s being stored in it, i.e. unknown variable = data=E2=80=A6=20 That being said, I completely disagree when it comes to storing and = retrieving information in a data structure. If i have a field in a data = structure (read: SQL data table or WebDNA database) that is for storing = dates, then allowing someone to store "yesterday" is nonsensical and = causes problems when I try to retrieve dates based on a calculation. = (i.e. leMODDATEdata=3D12/31/2015) Of course I should write code that = stops this data from being stored in the first place, but as a last = resort the database program itself should defend the database to protect = the integrity of the data stored in it. The side effect, which almost = outweighs the protection factor to be candid, is that when retrieving = info, if each field has a predefined data type, the database already = knows how to deal with searches so the programmer doesn't have to = reiterate for each search that this field is a date, or a number, or = whatever.=20 Just my two cents.=20 -Brian B. Burton > On Aug 31, 2016, at 2:57 PM, christophe.billiottet@webdna.us wrote: >=20 > I personally believe this extra flexibility allows to deal with = database content the way we want, and allows to treat a single field = either as a date, a number or a text field, or even the tree types in a = single page of code. >=20 > I think extra rigidity diminishes creativity, and what I like most in = WebDNA is that it behave like a "chameleon" language. It is so flexible = that you can do whatever you want with it, the way you want. >=20 > I would be interested to read what others have to say about this = requested modification, >=20 > - chris >=20 >=20 >=20 >=20 >=20 >> On Aug 31, 2016, at 20:08, Brian Burton wrote: >>=20 >> Over the years I=E2=80=99ve been bending WebDNA to my will. I=E2=80=99v= e more or less successfully implemented the view and controller ideology = of an MVC framework in WebDNA, and am getting ever closer to doing the = work to get data models working in webDNA. It=E2=80=99s so frustrating = in 2016 to not be able to tag a field in a database as unique or numeric = and let the language deal with it for you when you interact with the = database. I recently wasted more time then I care to admit to making = [delete db=3Dsomedb&leIDdata=3D10000] work because i forgot to add = &IDtype=3Dnum to the code. >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Brian Burton

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:

[SubTotal] ??? (1998) Summing fields (1997) Quotation Marks in Database (1998) WebMerchant 1.6 and SHTML (1997) [SHOWIF] (1997) help needed w/ search params (1998) Interesting speed comparison .. (2003) Help name our technology! (1997) check out page (SSL) *still* not loading on Netscape 4.0+ (1999) Bad dates/times on a Windows server? (2002) [WebDNA] Developer Resource Center Redirect (2008) RE: Emailer prefs in two places ... (1997) Where is f2? (1997) no global [username] or [password] displayed ... (1997) Shownext never shows next...still (1997) Sort Order on a page search (1997) [WebDNA] Permissions changing of .db (2013) WCS Newbie question (1997) problems with 2 tags (1997) WebCat2 several catalogs? (1997)