Re: [WebDNA] A new popuated field to a DB with 700.000 records
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 104080
interpreted = N
texte = just a quick thought/test - try that again but like this: [search db=l4.db&nel4_statusdata=dummy&asl4_serialsort=1][numFound] [foundItems][ReplaceFoundItems]l4_index=[index][/ReplaceFoundItems][/ foundItems] [/search] using [founditems] to wrap [ReplaceFoundItems] is dumb, but how to get the next val for the [l4_index] field with *min.* impact on webdna.. hmmm... Anyway, I *assume* that you are still better off with my above suggestion than with the nested [replace] which has to find the record all over again.. on each and every iteration. or take it down and do it in something offline (mac? filemaker?) and then fire it up again online.. having written code to populate the new records *as you create them*, at the time you [append], [replace .. &append=T]) -G On Dec 2, 2009, at 1:27 PM, Palle Bo Nielsen wrote: > Hi all, > > I got a DB which has 11 fields and more that 700.000 lines of data. > > Now I need to add a new field and I need to populate this field with > an index from the number 1 to the most recent number which for > example is 700.000. > > The number 1 is the first lines of data within this BD and the > 700.000 is the most recent added line of data. > > If have done some test and sand-boxing and every time WebDNA goes > into it's knees. > > I need some good advise from you all to figure out the best solution. > > I look forward to your suggestions. > > **** this one is rough and breaks WebDNA **** > [search db=l4.db&nel4_statusdata=dummy&asl4_serialsort=1][numFound] > [foundItems] > [replace db=l4.db&eql4_skudata=[l4_sku]]l4_index=[index][/replace] > [/foundItems][/search] > **** snip **** > > > Palle--------------------------------------------------------- > 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 > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 ------------ Govinda govinda.webdnatalk@gmail.com
Associated Messages, from the most recent to the oldest:
just a quick thought/test - try that again but like this: [search db=l4.db&nel4_statusdata=dummy&asl4_serialsort=1][numFound] [founditems][replacefounditems]l4_index=[index][/ReplaceFoundItems][/ foundItems] [/search] using [founditems] to wrap [replacefounditems] is dumb, but how to get the next val for the [l4_index] field with *min.* impact on webdna.. hmmm... Anyway, I *assume* that you are still better off with my above suggestion than with the nested [replace] which has to find the record all over again.. on each and every iteration. or take it down and do it in something offline (mac? filemaker?) and then fire it up again online.. having written code to populate the new records *as you create them*, at the time you [append], [replace .. &append=T]) -G On Dec 2, 2009, at 1:27 PM, Palle Bo Nielsen wrote: > Hi all, > > I got a DB which has 11 fields and more that 700.000 lines of data. > > Now I need to add a new field and I need to populate this field with > an index from the number 1 to the most recent number which for > example is 700.000. > > The number 1 is the first lines of data within this BD and the > 700.000 is the most recent added line of data. > > If have done some test and sand-boxing and every time WebDNA goes > into it's knees. > > I need some good advise from you all to figure out the best solution. > > I look forward to your suggestions. > > **** this one is rough and breaks WebDNA **** > [search db=l4.db&nel4_statusdata=dummy&asl4_serialsort=1][numFound] > [founditems] > [replace db=l4.db&eql4_skudata=[l4_sku]]l4_index=[index][/replace] > [/foundItems][/search] > **** snip **** > > > Palle--------------------------------------------------------- > 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 > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 ------------ Govinda govinda.webdnatalk@gmail.com
Govinda
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:
Tab Charactor (1997)
not interpreting Q (2001)
AutoCommit Preference? (1998)
READFILE command? (1998)
Xserve Recommendations (2003)
Wanted: Broader string manipulation functions (1997)
[WebDNA] Apache or Nginx (2016)
Email check problems (1999)
Details of shipping - Totalqty calculations (1997)
[WebDNA] HTTP post help (2012)
sort problems....bug or brain fart? (1997)
Convertchars Problem (2004)
Followup question re: checksum for credit cards? (1997)
WebCat2b12 forgets serial # (1997)
file browser. (2002)
shipcost (1997)
default value from Lookup (was Grant, please help me) (1997)
[Semi-OT] Kinda cool tool (how does it work?) (2004)
RE: Web*SSL and WebCatalog (1997)
[SearchString] problem with [search] context (1997)