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 = 104083
interpreted = N
texte = Govinda, Thanks for your suggestion, but [ReplaceFoundItems] does not help. = WebDNA goes on it's knees; even with or without the [foundItems]. Palle On 02/12/2009, at 21.50, Govinda wrote: > just a quick thought/test - try that again but like this: >=20 > [search db=3Dl4.db&nel4_statusdata=3Ddummy&asl4_serialsort=3D1][numFound= ] > = [foundItems][ReplaceFoundItems]l4_index=3D[index][/ReplaceFoundItems][/fou= ndItems] > [/search] >=20 > 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. >=20 > 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=3DT]) >=20 > -G >=20 > On Dec 2, 2009, at 1:27 PM, Palle Bo Nielsen wrote: >=20 >> Hi all, >>=20 >> I got a DB which has 11 fields and more that 700.000 lines of data. >>=20 >> 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. >>=20 >> The number 1 is the first lines of data within this BD and the = 700.000 is the most recent added line of data. >>=20 >> If have done some test and sand-boxing and every time WebDNA goes = into it's knees. >>=20 >> I need some good advise from you all to figure out the best solution. >>=20 >> I look forward to your suggestions. >>=20 >> **** this one is rough and breaks WebDNA **** >> [search = db=3Dl4.db&nel4_statusdata=3Ddummy&asl4_serialsort=3D1][numFound][foundIte= ms] >> [replace db=3Dl4.db&eql4_skudata=3D[l4_sku]]l4_index=3D[index][/replace= ] >> [/foundItems][/search] >> **** snip **** >>=20 >>=20 >> 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=3Dtopics&category=3D288 >=20 > ------------ > Govinda > govinda.webdnatalk@gmail.com >=20 >=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 > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288 >=20
Associated Messages, from the most recent to the oldest:
Govinda, Thanks for your suggestion, but [replacefounditems] does not help. = WebDNA goes on it's knees; even with or without the [founditems]. Palle On 02/12/2009, at 21.50, Govinda wrote: > just a quick thought/test - try that again but like this: >=20 > [search db=3Dl4.db&nel4_statusdata=3Ddummy&asl4_serialsort=3D1][numFound= ] > = [founditems][replacefounditems]l4_index=3D[index][/ReplaceFoundItems][/fou= ndItems] > [/search] >=20 > 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. >=20 > 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=3DT]) >=20 > -G >=20 > On Dec 2, 2009, at 1:27 PM, Palle Bo Nielsen wrote: >=20 >> Hi all, >>=20 >> I got a DB which has 11 fields and more that 700.000 lines of data. >>=20 >> 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. >>=20 >> The number 1 is the first lines of data within this BD and the = 700.000 is the most recent added line of data. >>=20 >> If have done some test and sand-boxing and every time WebDNA goes = into it's knees. >>=20 >> I need some good advise from you all to figure out the best solution. >>=20 >> I look forward to your suggestions. >>=20 >> **** this one is rough and breaks WebDNA **** >> [search = db=3Dl4.db&nel4_statusdata=3Ddummy&asl4_serialsort=3D1][numFound][foundIte= ms] >> [replace db=3Dl4.db&eql4_skudata=3D[l4_sku]]l4_index=3D[index][/replace= ] >> [/foundItems][/search] >> **** snip **** >>=20 >>=20 >> 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=3Dtopics&category=3D288 >=20 > ------------ > Govinda > govinda.webdnatalk@gmail.com >=20 >=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 > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category=3D288 >=20
Palle Bo Nielsen
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:
Image upload (2000)
Nested tags count question (1997)
searchable list archive (1997)
Browser Resolution (1999)
A question on sub-categories (1997)
[showif] or-ing (1999)
rotating thumbnails (1997)
Setting up WebCatalog with Retail Pro data (1996)
random random links (1999)
Format question WC Mac f3 (1997)
WebCat2final1 crashes (1997)
WebCatalog2 Feature Feedback (1996)
UPPERCASE (1997)
[WebDNA] Image resizing on the fly (2012)
html delivery (1997)
pc (1997)
database visibility (2000)
Sendmail Woes (2002)
Date Sorting (1997)
How fast is your server? (2002)