Re: [WebDNA] Error 500 with SUMM=T

This WebDNA talk-list message is from

2017


It keeps the original formatting.
numero = 113831
interpreted = N
texte = 1426 --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Here is a test that should determine whether it is a database content = problem: [closedatabase test.db] [writefile test.db]_email [/writefile] [loop start=3D1&end=3D15000][append = db=3Dtest.db]_email=3Dtest[math]floor([random = format=3Dfloat]*10000)[/math]@example.com[/append][/loop] [search db=3Dtest.db&ne_emaildata=3DFIND_ALL] [numfound] = raw[/search]
[search db=3Dtest.db&ne_emaildata=3DFIND_ALL&_emailSUMM=3DT] [numfound] = summarized[/search] This will create a database named =E2=80=9Ctest.db=E2=80=9D with one = field - =E2=80=9C_email=E2=80=9D, then add 15000 records with _email set = to a value like "test6746@example.com =E2=80=9D= , where the numeric portion is a random integer from zero to 9999, so = there will be duplicates. In my test on a linux server running WebDNA 8.5.1, it works fine, with = the raw results returning 15000 records, and the summarized results = varying from one run to the next, usually around 7800 unique values. My guess would be that this will work fine for you as well, and that = there is some data in the real database that WebDNA is choking on when = running the SUMM comparisons. I this is the case, then the next step = would be to split the real data into smaller subsets and run the test on = those until you can isolate what data is causing WebDNA problems. Then = Chris will have something specific to fix. - Brian Fries > On Dec 12, 2017, at 7:28 AM, Brian Harrington = wrote: >=20 > exactly what I've been saying... you all keep your little code a = secret and NO resource on the website, same site for 12 years! yelp... = just checked "search" on "sort" NO REF THERE! >=20 > So we all need to take notes...? >=20 >=20 >=20 > On Tue, Dec 12, 2017 at 12:04 PM, Kenneth Grome = > wrote: > > I see two problems with > > > > complex sort example: > > &email*S*sort=3D1&emailsdir=3Das > > (should be &emailsort=3D1&emailsdir=3Das) >=20 > I already corrected this typo in a later post ... :) >=20 >=20 > > simple sort example: > > &*as*emailsort=3D1 > > (should be &emailsort=3D1) >=20 > No it should not! >=20 > You're saying this because you do not know how to write simpler > sort code. And that's why I posted this example ... so you and > Lawrence (and anyone else who does not know this) might learn how > to do it. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us = > archives: http://www.webdna.us/page.dna?numero=3D55 = > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Here is a test that should determine whether = it is a database content problem:


[closedatabase test.db]
[writefile = test.db]_email
[/writefile]
[loop start=3D1&end=3D15000][append = db=3Dtest.db]_email=3Dtest[math]floor([random = format=3Dfloat]*10000)[/math]@example.com[/append][/loop]
[search db=3Dtest.db&ne_emaildata=3DFIND_ALL] [numfound] = raw[/search]<br>
[search = db=3Dtest.db&ne_emaildata=3DFIND_ALL&_emailSUMM=3DT] [numfound] = summarized[/search]


This will create a = database named =E2=80=9Ctest.db=E2=80=9D with one field - =E2=80=9C_email=E2= =80=9D, then add 15000 records with _email set to a value like "test6746@example.com=E2=80=9D, where the numeric portion = is a random integer from zero to 9999, so there will be = duplicates.

In = my test on a linux server running WebDNA 8.5.1, it works fine, with the = raw results returning 15000 records, and the summarized results varying = from one run to the next, usually around 7800 unique values.

My guess would be that = this will work fine for you as well, and that there is some data in the = real database that WebDNA is choking on when running the SUMM = comparisons. I this is the case, then the next step would be to split = the real data into smaller subsets and run the test on those until you = can isolate what data is causing WebDNA problems. Then Chris will have = something specific to fix.

- = Brian Fries


On = Dec 12, 2017, at 7:28 AM, Brian Harrington <autoglasswny@gmail.com> wrote:

exactly what I've been saying... you all keep your little = code a secret and NO resource on the website,  same site for 12 = years! yelp... just checked "search" on "sort" NO REF THERE!

So we all need to take = notes...?


On Tue, Dec 12, 2017 at 12:04 PM, = Kenneth Grome <ken@webdnasolutions.com> wrote:
> = I see two problems with
>
> complex sort example:
> &email*S*sort=3D1&emailsdir=3Das
> (should be &emailsort=3D1&emailsdir=3Das)

I already corrected this typo in a later post ... :)


> simple sort example:
> &*as*emailsort=3D1
> (should be &emailsort=3D1)

No it should not!

You're saying this because you do not know how to write simpler
sort code.  And that's why I posted this example ... so you and
Lawrence (and anyone else who does not know this) might learn how
to do it.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  2. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  3. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  4. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  5. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  6. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  7. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  8. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  9. Re: [WebDNA] Error 500 with SUMM=T (Christer Olsson 2017)
  10. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  11. Re: [WebDNA] Error 500 with SUMM=T (Christer Olsson 2017)
  12. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  13. Re: [WebDNA] Error 500 with SUMM=T (Christer Olsson 2017)
  14. Re: [WebDNA] Error 500 with SUMM=T (Christer Olsson 2017)
  15. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  16. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  17. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  18. Re: [WebDNA] Error 500 with SUMM=T (Stuart Tremain 2017)
  19. Re: [WebDNA] Error 500 with SUMM=T (Stuart Tremain 2017)
  20. Re: [WebDNA] Error 500 with SUMM=T (Stuart Tremain 2017)
  21. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  22. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  23. Re: [WebDNA] Error 500 with SUMM=T (Brian Fries 2017)
  24. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  25. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  26. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  27. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  28. Re: [WebDNA] Error 500 with SUMM=T (Brian Fries 2017)
  29. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  30. Re: [WebDNA] Error 500 with SUMM=T (Brian Fries 2017)
  31. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  32. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  33. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  34. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  35. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  36. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  37. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  38. [BULK] Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  39. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  40. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  41. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  42. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  43. Re: [WebDNA] Error 500 with SUMM=T ("Lawrence Banahan - Author's Image" 2017)
  44. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  45. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  46. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  47. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  48. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  49. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  50. Re: [WebDNA] Error 500 with SUMM=T (Kenneth Grome 2017)
  51. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  52. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  53. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  54. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  55. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  56. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  57. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  58. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  59. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  60. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  61. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  62. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  63. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  64. Re: [WebDNA] Error 500 with SUMM=T (Brian Harrington 2017)
  65. Re: [WebDNA] Error 500 with SUMM=T (christophe.billiottet@webdna.us 2017)
  66. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  67. Re: [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
  68. Re: [WebDNA] Error 500 with SUMM=T (Brian Fries 2017)
  69. Re: [WebDNA] Error 500 with SUMM=T (Stuart Tremain 2017)
  70. [WebDNA] Error 500 with SUMM=T (Lawrence Banahan 2017)
1426 --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Here is a test that should determine whether it is a database content = problem: [closedatabase test.db] [writefile test.db]_email [/writefile] [loop start=3D1&end=3D15000][append = db=3Dtest.db]_email=3Dtest[math]floor([random = format=3Dfloat]*10000)[/math]@example.com[/append][/loop] [search db=3Dtest.db&ne_emaildata=3DFIND_ALL] [numfound] = raw[/search]
[search db=3Dtest.db&ne_emaildata=3DFIND_ALL&_emailSUMM=3DT] [numfound] = summarized[/search] This will create a database named =E2=80=9Ctest.db=E2=80=9D with one = field - =E2=80=9C_email=E2=80=9D, then add 15000 records with _email set = to a value like "test6746@example.com =E2=80=9D= , where the numeric portion is a random integer from zero to 9999, so = there will be duplicates. In my test on a linux server running WebDNA 8.5.1, it works fine, with = the raw results returning 15000 records, and the summarized results = varying from one run to the next, usually around 7800 unique values. My guess would be that this will work fine for you as well, and that = there is some data in the real database that WebDNA is choking on when = running the SUMM comparisons. I this is the case, then the next step = would be to split the real data into smaller subsets and run the test on = those until you can isolate what data is causing WebDNA problems. Then = Chris will have something specific to fix. - Brian Fries > On Dec 12, 2017, at 7:28 AM, Brian Harrington = wrote: >=20 > exactly what I've been saying... you all keep your little code a = secret and NO resource on the website, same site for 12 years! yelp... = just checked "search" on "sort" NO REF THERE! >=20 > So we all need to take notes...? >=20 >=20 >=20 > On Tue, Dec 12, 2017 at 12:04 PM, Kenneth Grome = > wrote: > > I see two problems with > > > > complex sort example: > > &email*S*sort=3D1&emailsdir=3Das > > (should be &emailsort=3D1&emailsdir=3Das) >=20 > I already corrected this typo in a later post ... :) >=20 >=20 > > simple sort example: > > &*as*emailsort=3D1 > > (should be &emailsort=3D1) >=20 > No it should not! >=20 > You're saying this because you do not know how to write simpler > sort code. And that's why I posted this example ... so you and > Lawrence (and anyone else who does not know this) might learn how > to do it. >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us = > archives: http://www.webdna.us/page.dna?numero=3D55 = > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Here is a test that should determine whether = it is a database content problem:


[closedatabase test.db]
[writefile = test.db]_email
[/writefile]
[loop start=3D1&end=3D15000][append = db=3Dtest.db]_email=3Dtest[math]floor([random = format=3Dfloat]*10000)[/math]@example.com[/append][/loop]
[search db=3Dtest.db&ne_emaildata=3DFIND_ALL] [numfound] = raw[/search]<br>
[search = db=3Dtest.db&ne_emaildata=3DFIND_ALL&_emailSUMM=3DT] [numfound] = summarized[/search]


This will create a = database named =E2=80=9Ctest.db=E2=80=9D with one field - =E2=80=9C_email=E2= =80=9D, then add 15000 records with _email set to a value like "test6746@example.com=E2=80=9D, where the numeric portion = is a random integer from zero to 9999, so there will be = duplicates.

In = my test on a linux server running WebDNA 8.5.1, it works fine, with the = raw results returning 15000 records, and the summarized results varying = from one run to the next, usually around 7800 unique values.

My guess would be that = this will work fine for you as well, and that there is some data in the = real database that WebDNA is choking on when running the SUMM = comparisons. I this is the case, then the next step would be to split = the real data into smaller subsets and run the test on those until you = can isolate what data is causing WebDNA problems. Then Chris will have = something specific to fix.

- = Brian Fries


On = Dec 12, 2017, at 7:28 AM, Brian Harrington <autoglasswny@gmail.com> wrote:

exactly what I've been saying... you all keep your little = code a secret and NO resource on the website,  same site for 12 = years! yelp... just checked "search" on "sort" NO REF THERE!

So we all need to take = notes...?


On Tue, Dec 12, 2017 at 12:04 PM, = Kenneth Grome <ken@webdnasolutions.com> wrote:
> = I see two problems with
>
> complex sort example:
> &email*S*sort=3D1&emailsdir=3Das
> (should be &emailsort=3D1&emailsdir=3Das)

I already corrected this typo in a later post ... :)


> simple sort example:
> &*as*emailsort=3D1
> (should be &emailsort=3D1)

No it should not!

You're saying this because you do not know how to write simpler
sort code.  And that's why I posted this example ... so you and
Lawrence (and anyone else who does not know this) might learn how
to do it.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_47C7297E-5A4B-4849-B11F-958E519526DD-- . 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:

Line Breaks (2003) Email Set-Up? (1997) shownext example (2001) Problem (1997) Re:listfiles-looking for slick solution (1997) Further on formula.db failure to calculate shipCost (1997) New syntax feedback for 4.0 (2000) Setting up WebCatalog with Retail Pro data (1996) [OT] XML data to tab delimited database (2003) Removing a character (2000) [WebDNA] PCI Vulnerability testing (2009) triggers (2003) Num Sort Descending (2004) OT: anyone know how to prevent image hijacking with Apache? (2002) Photo Album (2000) All choices on IE different than Netscape (1997) More news on 5.0 (2003) Variable Math (1998) Resume Catalog ? (1997) multiple credit card merchant accounts/processors (1997)