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:
Single Link browsing (1997)
ShowNext example for GeneralStore (1997)
Moment of Thanks (1997)
Strange error (2000)
Using the new syntax/scoping methods (2000)
webdelivery.html and webna (1997)
all records returned. (1997)
Am I going senile? (Price recalc based on quantity) (1997)
WebCommerce: Folder organization ? (1997)
Navigator 4.01 (1997)
Sort Order on a page search (1997)
$purchase WITHOUT creditcar (1997)
Product Value Changes (2000)
Error Log.db --however (1997)
Date search - yes or no (1997)
catagories (1997)
MacOS X 10.2.2 (2002)
upgrading (1997)
File Upload (1997)
Odd error in logs (1998)