Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] MySQL Users
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106970
interpreted = N
texte = Here's one to spark your imagination, Donovan=85=20I've been known to have code in one place that decides whether it's =using a db or a table:[text]tDBPath=3D[if ==85][then]db=3Dmy.db[/then][else]table=3Dmytable[/else][/if][/text]=85 then later use that in a search:[search [tDBPath]&wofielddata=3D=85]=85 It would be nice to be able to then use listfields:[listfields [tDBPath]][fieldname]=3D[interpret][[fieldname]][/interpret]
[/listfields]Sure there are workarounds, but every WebDNA tag that takes a "db" =parameter should alternatively take a "table" parameter so consistent =coding can be used / reused.Brian FriesBrainScan SoftwareOn Jul 15, 2011, at 12:19 PM, Govinda wrote:> that is a good workaround, Donovan. :-)>=20> The main need I had for listfields with tables.. was for debugging. - = One short script to debug any table (spit out all its .hdr and =records).> Sure I could write it another way.. like using your suggestion too.. =but we have been relying on listfields for years.. and it was just =knee-jerk-natural to reach for it when using [table]s too.>=20> - Govinda> --------------> Old WebDNA talklist archives:> http://dev.webdna.us/TalkListArchive/index.tpl?db=3Dwebdna-talk>=20>=20>> Personally, I can't imagine a need for [listfields..] to work with =[table..], because tables only persist in the scope of a page/process.>>=20>> If you need to list the fields after the table has been defined, I =would initiate them with a text context:>>=20>> ---------->> [text]t_fields=3Did,name[/text]>> [table name=3Dtb_test&fields=3D[t_fields]]>> 1Fred>> 2john>> [/table]>>=20>> [listwords words=3D[t_fields]]>> [word]
>> [/listwords]>> ---------->>=20>>=20>> Donovan>>=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
Associated Messages, from the most recent to the oldest:
Here's one to spark your imagination, Donovan=85=20I've been known to have code in one place that decides whether it's =using a db or a table:[text]tDBPath=3D[if ==85][then]db=3Dmy.db[/then][else]table=3Dmytable[/else][/if][/text]=85 then later use that in a search:[search [tDBPath]&wofielddata=3D=85]=85 It would be nice to be able to then use listfields:[listfields [tDBPath]][fieldname]=3D[interpret][[fieldname]][/interpret]
[/listfields]Sure there are workarounds, but every WebDNA tag that takes a "db" =parameter should alternatively take a "table" parameter so consistent =coding can be used / reused.Brian FriesBrainScan SoftwareOn Jul 15, 2011, at 12:19 PM, Govinda wrote:> that is a good workaround, Donovan. :-)>=20> The main need I had for listfields with tables.. was for debugging. - = One short script to debug any table (spit out all its .hdr and =records).> Sure I could write it another way.. like using your suggestion too.. =but we have been relying on listfields for years.. and it was just =knee-jerk-natural to reach for it when using [table]s too.>=20> - Govinda> --------------> Old WebDNA talklist archives:> http://dev.webdna.us/TalkListArchive/index.tpl?db=3Dwebdna-talk>=20>=20>> Personally, I can't imagine a need for [listfields..] to work with =[table..], because tables only persist in the scope of a page/process.>>=20>> If you need to list the fields after the table has been defined, I =would initiate them with a text context:>>=20>> ---------->> [text]t_fields=3Did,name[/text]>> [table name=3Dtb_test&fields=3D[t_fields]]>> 1Fred>> 2john>> [/table]>>=20>> [listwords words=3D[t_fields]]>> [word]
>> [/listwords]>> ---------->>=20>>=20>> Donovan>>=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
Brian Fries
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:
WebCat2b12 CGI Mac -- Problems propagating the cart through frames...still (1997)
Size limit for tmpl editor ? (1997)
ups calculator (2000)
Include a big block of text (1997)
WC1.6 to WC2 date formatting (1997)
& Problem in Textarea (1999)
Is this possible, WebCat2.0 and checkboxes (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
[defined]ish (1997)
[WebDNA] fastcgi 7+ & [cart]? (2010)
[LOOKUP] (1997)
Flush - Updates made but not shown (2002)
[OT] - CyberCash/Verisign (2001)
[isfile] ? (1997)
Looking up two prices in Formulas.db (1997)
Waitfor file (2000)
Allowed fields in formulas.db (1998)
Interfacing WebMerchant to www.fedex.com (1997)
Globals folder... (2003)
WebCat 4 / 4.5 License for sale! (2003)