Re: [WebDNA] Wishlist: ignore whitespace in database changes
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112944
interpreted = N
texte = 531 A long time ago I suggested a preference we could set to "T" to make WebDNA identify db fields by their prefixes. This might be the easiest way for us to use such a system, assuming we control our own field names, because we can instantly recognize the field type by its name: n.fieldname =3D number d.fieldname =3D date a.fieldname =3D alpha (or fieldname =3D alpha) In this simple system WebDNA would treat a fieldname that begins with "n." as numeric and "d." as a date, but only when this new preference is set to "T". The "a." prefix would be optional, and any field name not prefixed with "n." or "d." would be treated as alphabetical. --- Another method of implementation might be to use a new ".type" file that is related to a specific db, similar to the way the ".hdr" file is related to a specific db. For a loginCodes.db this new type file would be named "loginCodes.type". When this file exist in the same folder as its corresponding db WebDNA would automatically identify the field types based on the settings in this file. If the file does not exist or is not in the same folder as the db, WebDNA would behave as it does now. --- Either of these implementations will preserves the current behavior of WebDNA while adding a new capability for those who wish to use it. There are probably issues and limitations to consider in either system, but at least this gives you a couple ideas to consider ... But first PLEASE add a "table=3D" parameter to listfields so we can use it to create our own debugging code for WebDNA tables. I find it hard to believe that this feature does not already exist! Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 08/31/2016 02:57 PM, christophe.billiottet@webdna.us wrote: > I personally believe this extra flexibility allows to deal with databas= e 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 W= ebDNA is that it behave like a "chameleon" language. It is so flexible th= at 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 reques= ted modification, >=20 > - chris >=20 >=20 >=20 >=20 >=20 >> On Aug 31, 2016, at 20:08, Brian Burton
wrote: >> >> Over the years I=E2=80=99ve been bending WebDNA to my will. I=E2=80=99= ve more or less successfully implemented the view and controller ideology= of an MVC framework in WebDNA, and am getting ever closer to doing the w= ork 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 databas= e. I recently wasted more time then I care to admit to making [delete db=3D= somedb&leIDdata=3D10000] work because i forgot to add &IDtype=3Dnum to th= e 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 >=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 .
Associated Messages, from the most recent to the oldest:
531 A long time ago I suggested a preference we could set to "T" to make WebDNA identify db fields by their prefixes. This might be the easiest way for us to use such a system, assuming we control our own field names, because we can instantly recognize the field type by its name: n.fieldname =3D number d.fieldname =3D date a.fieldname =3D alpha (or fieldname =3D alpha) In this simple system WebDNA would treat a fieldname that begins with "n." as numeric and "d." as a date, but only when this new preference is set to "T". The "a." prefix would be optional, and any field name not prefixed with "n." or "d." would be treated as alphabetical. --- Another method of implementation might be to use a new ".type" file that is related to a specific db, similar to the way the ".hdr" file is related to a specific db. For a loginCodes.db this new type file would be named "loginCodes.type". When this file exist in the same folder as its corresponding db WebDNA would automatically identify the field types based on the settings in this file. If the file does not exist or is not in the same folder as the db, WebDNA would behave as it does now. --- Either of these implementations will preserves the current behavior of WebDNA while adding a new capability for those who wish to use it. There are probably issues and limitations to consider in either system, but at least this gives you a couple ideas to consider ... But first PLEASE add a "table=3D" parameter to listfields so we can use it to create our own debugging code for WebDNA tables. I find it hard to believe that this feature does not already exist! Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 08/31/2016 02:57 PM, christophe.billiottet@webdna.us wrote: > I personally believe this extra flexibility allows to deal with databas= e 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 W= ebDNA is that it behave like a "chameleon" language. It is so flexible th= at 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 reques= ted modification, >=20 > - chris >=20 >=20 >=20 >=20 >=20 >> On Aug 31, 2016, at 20:08, Brian Burton wrote: >> >> Over the years I=E2=80=99ve been bending WebDNA to my will. I=E2=80=99= ve more or less successfully implemented the view and controller ideology= of an MVC framework in WebDNA, and am getting ever closer to doing the w= ork 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 databas= e. I recently wasted more time then I care to admit to making [delete db=3D= somedb&leIDdata=3D10000] work because i forgot to add &IDtype=3Dnum to th= e 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 >=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 .
Kenneth Grome
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:
Version 2.0 and 1.6 simultaneous (1997)
Summing fields (1997)
Help! WebCat2 bug (1997)
Secure Sever and showcart errors (1997)
Grouping fields help (2004)
Nested search (1997)
Help! WebCat2 bug (1997)
[WebDNA] email server (2011)
Prevent multiple appends with Reload Button (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Return records from another (1997)
Dates (1998)
Menu Syntax on Edit/Add templates (1998)
Preserving form data (1999)
Bug? (1997)
List of WebDNA users - Show of Hands (2002)
emailer w/F2 (1997)
[WebDNA] Double sendmails (2014)
[WriteFile] problems (1997)
Announcing general availabilty of WebDNA 4.5 release (2002)