Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT]

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106971
interpreted = N
texte = Brian Fries wrote: > Here's one to spark your imagination, Donovan… > > I've been known to have code in one place that decides whether it's using a db or a table: > > [text]tDBPath=[if …][then]db=my.db[/then][else]table=mytable[/else][/if][/text] > > … then later use that in a search: > > [search [tDBPath]&wofielddata=…] > > … It would be nice to be able to then use listfields: > > [listfields [tDBPath]] > [fieldname]=[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 Fries > BrainScan Software Hey!, I've seen that style of coding before.. somewhere? ;-) I see a point to it, don't get me wrong. I think a "fix" like this would likely come down to priorities and policy however. "It's a workable idea, but is it really needed right now?" sort of thing. Note, WSC would have to change [listdatabases...] as well. Anyway, as Brian mentioned, even with his complex style of coding, a global listfiles type of feature could be accommodated with some key naming conventions set.: ---------------- [text]tf_mytable=id,name[/text] [table name=tb_test&fields=[tf_mytable]] 1Fred 2john [/table] [text]tDBPath=[if …][then]db=my.db[/then][else]table=mytable[/else][/if][/text] [if "[tDBPath]"^".db"] [then] [listfields [tDBPath]] [fieldname]=[interpret][[fieldname]][/interpret]
[/listfields] [/then] [else] [listwords words=[interpret][tf_[tDBPath]][/interpret]] [word]
[/listwords] [/else] [/if] ---------------- You could shorten the use of this feature up with your own function [db_listfields ..] Note, I don't officially work for WSC right at this time, so these are just my *developer* opinions. Donovan -- Donovan Brooke **[Square Bracket Utopia]** Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] MySQL Users (Kenneth Grome 2011)
  2. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] (Donovan Brooke 2011)
  3. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] (Donovan Brooke 2011)
  4. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] MySQL Users (Brian Fries 2011)
  5. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] (Donovan Brooke 2011)
  6. Re: [WebDNA] Now: Listfields does not work with tables - Was: [OT] MySQL Users (Govinda 2011)
  7. [WebDNA] Now: Listfields does not work with tables - Was: [OT] MySQL Users (Donovan Brooke 2011)
Brian Fries wrote: > Here's one to spark your imagination, Donovan… > > I've been known to have code in one place that decides whether it's using a db or a table: > > [text]tDBPath=[if …][then]db=my.db[/then][else]table=mytable[/else][/if][/text] > > … then later use that in a search: > > [search [tDBPath]&wofielddata=…] > > … It would be nice to be able to then use listfields: > > [listfields [tDBPath]] > [fieldname]=[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 Fries > BrainScan Software Hey!, I've seen that style of coding before.. somewhere? ;-) I see a point to it, don't get me wrong. I think a "fix" like this would likely come down to priorities and policy however. "It's a workable idea, but is it really needed right now?" sort of thing. Note, WSC would have to change [listdatabases...] as well. Anyway, as Brian mentioned, even with his complex style of coding, a global listfiles type of feature could be accommodated with some key naming conventions set.: ---------------- [text]tf_mytable=id,name[/text] [table name=tb_test&fields=[tf_mytable]] 1Fred 2john [/table] [text]tDBPath=[if …][then]db=my.db[/then][else]table=mytable[/else][/if][/text] [if "[tDBPath]"^".db"] [then] [listfields [tDBPath]] [fieldname]=[interpret][[fieldname]][/interpret]
[/listfields] [/then] [else] [listwords words=[interpret][tf_[tDBPath]][/interpret]] [word]
[/listwords] [/else] [/if] ---------------- You could shorten the use of this feature up with your own function [db_listfields ..] Note, I don't officially work for WSC right at this time, so these are just my *developer* opinions. Donovan -- Donovan Brooke **[Square Bracket Utopia]** Donovan Brooke

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:

WebCat2 Append problem (B14Macacgi) (1997) Just Testing (1997) [WebDNA] OT - JS help (2008) Snake Bites (1997) [LOOKUP] (1997) Date field search needs ... (1998) Why isn't this working (1999) Re:2nd WebCatalog2 Feature Request (1996) Webcat & SIMS (1998) problems with 2 tags (1997) Big Databases (1997) Loss in Form (1998) new WebDNA 5 command reference (2003) Help! WebCat2 bug (1997) Fwd: [WebDNA] Fails to recognize comma-separated db (2010) PCS Emailer's role ? (1997) Error.html (1997) Change history ... ? (2003) Server crash (1997) another problem (1997)