Re: Feature Request: [moverecord]

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 52162
interpreted = N
texte = then add [delete db=xx.db&eqIddata=[theid]] after the [/search]... The cool thing about WebDNA 5 functions is that you can essentially customize the language to your heart's desire. With a wee bit more work you could write a generic version of a "moverecord" function that could work for any database via a creative use of [listfields]. - brian On Monday, August 11, 2003, at 09:12 AM, WJ Starck wrote: > Except that doesn't delete the moved records from the old db... > > Regards, > > -- > > Will Starck > NovaDerm Skincare Science > http://www.novaderm.com > wjs@novaderm.com > > > > On Monday, August 11, 2003, at 11:06 AM, Donovan wrote: > >> Hows 'bout: >> >> [function name=moverecord] >> [Search db=xx.db&eqIDdata=[theID]] >> [FoundItems] >> [Replace >> db=YY.db&eqIDdata=[theID]]field1=[field1]&field2=[field2][/Replace] >> [/FoundItems] >> [/Search] >> [/function] >> >> >> Then call like: >> [moverecord theID=[theID]] >> >> Donovan >> >> >> >> >> WJ Starck wrote: >>> It'd be nice if WebDNA had a [moverecord] context that would move >>> records from one db to another, and then delete the moved records >>> from the first db. >>> Something like >>> [moverecord >>> from=db1&to=db2&eqrecordiddatarq=[recordid]]field1=[field1]&field2=[f >>> iel d2]...[/moverecord] >>> Where recordid could be any search parameter(s) as in the [replace] >>> context >>> This would be nice for archiving database records to trim the size >>> of existing databases to increase performance. >>> Also, It'd be great this context would create the "to" file by >>> copying the database headers from the "from" file if the "to" file >>> doesn't already exist. >>> Regards, >>> -- > > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Feature Request: [moverecord] ( Phillip Bonesteele 2003)
  2. Re: Feature Request: [moverecord] ( WJ Starck 2003)
  3. Re: Feature Request: [moverecord] ( Brian Fries 2003)
  4. Re: Feature Request: [moverecord] ( WJ Starck 2003)
  5. Re: Feature Request: [moverecord] ( Donovan 2003)
  6. Feature Request: [moverecord] ( WJ Starck 2003)
then add [delete db=xx.db&eqIddata=[theid]] after the [/search]... The cool thing about WebDNA 5 functions is that you can essentially customize the language to your heart's desire. With a wee bit more work you could write a generic version of a "moverecord" function that could work for any database via a creative use of [listfields]. - brian On Monday, August 11, 2003, at 09:12 AM, WJ Starck wrote: > Except that doesn't delete the moved records from the old db... > > Regards, > > -- > > Will Starck > NovaDerm Skincare Science > http://www.novaderm.com > wjs@novaderm.com > > > > On Monday, August 11, 2003, at 11:06 AM, Donovan wrote: > >> Hows 'bout: >> >> [function name=moverecord] >> [Search db=xx.db&eqIDdata=[theID]] >> [founditems] >> [Replace >> db=YY.db&eqIDdata=[theID]]field1=[field1]&field2=[field2][/Replace] >> [/FoundItems] >> [/Search] >> [/function] >> >> >> Then call like: >> [moverecord theID=[theID]] >> >> Donovan >> >> >> >> >> WJ Starck wrote: >>> It'd be nice if WebDNA had a [moverecord] context that would move >>> records from one db to another, and then delete the moved records >>> from the first db. >>> Something like >>> [moverecord >>> from=db1&to=db2&eqrecordiddatarq=[recordid]]field1=[field1]&field2=[f >>> iel d2]...[/moverecord] >>> Where recordid could be any search parameter(s) as in the [replace] >>> context >>> This would be nice for archiving database records to trim the size >>> of existing databases to increase performance. >>> Also, It'd be great this context would create the "to" file by >>> copying the database headers from the "from" file if the "to" file >>> doesn't already exist. >>> Regards, >>> -- > > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ 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:

Nesting format tags (1997) emailer w/F2 (1997) Quit revisited (1997) [WebDNA] Apache 2 Error Log Entry (2009) [WebDNA] Populate Bootstrap Modal with AJAX WebDNA (2015) Shopping Cart Directory (2000) Navigator 4.01 (1997) Emailer 1.0.2 Conflicts? (1998) [LOOKUP] (1997) Max Record length (1997) Format of Required fields error message (1997) PhotoMill -> PhotoMaster (1997) RE: High ASCII inside [LOOKUP] inside [LISTWORDS] (1998) RE: Displaying Location (1997) PCS Frames (1997) NTbeta18 corrupted? (1997) WebCatalog can't find database (1997) Time Remaining? (1998) PCS Frames-Default page is solution! (1997) # fields limited? (1997)