Re: [WebDNA] JSONStore Levels

This WebDNA talk-list message is from

2020


It keeps the original formatting.
numero = 115106
interpreted = N
texte = 2735 --000000000000a8dfdf05a5335138 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Chris, This all sounds great. I would suggest just replace the existing [jsonstore] tag. The only question I have left is if there is a colon in the node name what syntax would we use to get the value? Sorry but I have one API that I deal with where they include colons in the node names for some stooopid reason. Thanks - Tom Duke On Sat, 9 May 2020 at 09:17, wrote: > To answer the questions: > > =E2=80=A2 Will the code work for nested arrays? > Yes, it will flatten the array and save it in the database with > the full path name for each node. > > =E2=80=A2 Will it allow for JSON that has colons - or any character -= in the > node names? > Everything should be fine except tabs/linefeeds/etc. > > Using that example (adding double quotes around duration to make the JSON > valid), it would be saved in the database with the following column > names=3Dvalues > list:0:points.bean.pointsBase:0:time=3D2000 > list:0:points.bean.pointsBase:0:caption=3Dcaption text > list:0:points.bean.pointsBase:0:duration=3D5000 > list:0:points.bean.pointsBase:1:time=3D6000 > list:0:points.bean.pointsBase:1:caption=3Dcaption text > list:0:points.bean.pointsBase:1:duration=3D3000 > > The improved JSON parsing would take care of the bugs on the test suite > page. The unwanted whitespace would be fixed, and I believe the escaped > quotes would be handled correctly too. > > What would we call this? The behavior will be quite different than the > original [JSONSTORE] : should we name it something else like > [JSONSTOREPLUS], or replace the original? > > - chris--------------------------------------------------------- > 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 > --000000000000a8dfdf05a5335138 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Chris,

This all sounds great.=C2=A0 I w= ould suggest just replace the existing [jsonstore] tag.

The only question=C2=A0I have left is if there is a colon in the node= name what syntax would we use to get the value?=C2=A0 Sorry but I have one= API that I deal with where they include=C2=A0colons in the node names for = some stooopid reason.

Thanks
- Tom Duke<= br clear=3D"all">




On Sat, 9 May 2020 at 09:17, <talk@webdna.us> wrote:
= To answer the questions:

=C2=A0 =C2=A0 =E2=80=A2 Will the code work for nested arrays?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yes, it will flatten the array and save it in t= he database with the full path name for each node.

=C2=A0 =C2=A0 =E2=80=A2 Will it allow for JSON that has colons - or any cha= racter - in the node names?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Everything should be fine except tabs/linefeeds= /etc.

Using that example (adding double quotes around duration to make the JSON v= alid), it would be saved in the database with the following column names=3D= values
list:0:points.bean.pointsBase:0:time=3D2000
list:0:points.bean.pointsBase:0:caption=3Dcaption text
list:0:points.bean.pointsBase:0:duration=3D5000
list:0:points.bean.pointsBase:1:time=3D6000
list:0:points.bean.pointsBase:1:caption=3Dcaption text
list:0:points.bean.pointsBase:1:duration=3D3000

The improved JSON parsing would take care of the bugs on the test suite pag= e. The unwanted whitespace would be fixed, and I believe the escaped quotes= would be handled correctly too.

What would we call this? The behavior will be quite different than the orig= inal [JSONSTORE] : should we name it something else like [JSONSTOREPLUS], o= r replace the original?

- chris---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@w= ebdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: suppo= rt@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 --000000000000a8dfdf05a5335138-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  2. Re: [WebDNA] JSONStore Levels (Tom Duke 2020)
  3. Re: [WebDNA] JSONStore Levels (christophe.billiottet@webdna.us 2020)
  4. Re: [WebDNA] JSONStore Levels (Tom Duke 2020)
  5. Re: [WebDNA] JSONStore Levels (christophe.billiottet@webdna.us 2020)
  6. Re: [WebDNA] JSONStore Levels (christophe.billiottet@webdna.us 2020)
  7. Re: [WebDNA] JSONStore Levels (Michael Davis 2020)
  8. Re: [WebDNA] JSONStore Levels (Tom Duke 2020)
  9. Re: [WebDNA] JSONStore Levels (Michael Davis 2020)
  10. Re: [WebDNA] JSONStore Levels (Tom Duke 2020)
  11. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  12. Re: [WebDNA] JSONStore Levels (christophe.billiottet@webdna.us 2020)
  13. RE: [WebDNA] JSONStore Levels ("Scott @ Itsula" 2020)
  14. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  15. Re: [WebDNA] JSONStore Levels (Michael Davis 2020)
  16. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  17. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  18. Re: [WebDNA] JSONStore Levels (Michael Davis 2020)
  19. Re: [WebDNA] JSONStore Levels (Stuart Tremain 2020)
  20. [WebDNA] JSONStore Levels (Michael Davis 2020)
2735 --000000000000a8dfdf05a5335138 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Chris, This all sounds great. I would suggest just replace the existing [JSONstore] tag. The only question I have left is if there is a colon in the node name what syntax would we use to get the value? Sorry but I have one API that I deal with where they include colons in the node names for some stooopid reason. Thanks - Tom Duke On Sat, 9 May 2020 at 09:17, wrote: > To answer the questions: > > =E2=80=A2 Will the code work for nested arrays? > Yes, it will flatten the array and save it in the database with > the full path name for each node. > > =E2=80=A2 Will it allow for JSON that has colons - or any character -= in the > node names? > Everything should be fine except tabs/linefeeds/etc. > > Using that example (adding double quotes around duration to make the JSON > valid), it would be saved in the database with the following column > names=3Dvalues > list:0:points.bean.pointsBase:0:time=3D2000 > list:0:points.bean.pointsBase:0:caption=3Dcaption text > list:0:points.bean.pointsBase:0:duration=3D5000 > list:0:points.bean.pointsBase:1:time=3D6000 > list:0:points.bean.pointsBase:1:caption=3Dcaption text > list:0:points.bean.pointsBase:1:duration=3D3000 > > The improved JSON parsing would take care of the bugs on the test suite > page. The unwanted whitespace would be fixed, and I believe the escaped > quotes would be handled correctly too. > > What would we call this? The behavior will be quite different than the > original [JSONstore] : should we name it something else like > [JSONSTOREPLUS], or replace the original? > > - chris--------------------------------------------------------- > 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 > --000000000000a8dfdf05a5335138 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Chris,

This all sounds great.=C2=A0 I w= ould suggest just replace the existing [JSONstore] tag.

The only question=C2=A0I have left is if there is a colon in the node= name what syntax would we use to get the value?=C2=A0 Sorry but I have one= API that I deal with where they include=C2=A0colons in the node names for = some stooopid reason.

Thanks
- Tom Duke<= br clear=3D"all">




On Sat, 9 May 2020 at 09:17, <talk@webdna.us> wrote:
= To answer the questions:

=C2=A0 =C2=A0 =E2=80=A2 Will the code work for nested arrays?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yes, it will flatten the array and save it in t= he database with the full path name for each node.

=C2=A0 =C2=A0 =E2=80=A2 Will it allow for JSON that has colons - or any cha= racter - in the node names?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Everything should be fine except tabs/linefeeds= /etc.

Using that example (adding double quotes around duration to make the JSON v= alid), it would be saved in the database with the following column names=3D= values
list:0:points.bean.pointsBase:0:time=3D2000
list:0:points.bean.pointsBase:0:caption=3Dcaption text
list:0:points.bean.pointsBase:0:duration=3D5000
list:0:points.bean.pointsBase:1:time=3D6000
list:0:points.bean.pointsBase:1:caption=3Dcaption text
list:0:points.bean.pointsBase:1:duration=3D3000

The improved JSON parsing would take care of the bugs on the test suite pag= e. The unwanted whitespace would be fixed, and I believe the escaped quotes= would be handled correctly too.

What would we call this? The behavior will be quite different than the orig= inal [JSONstore] : should we name it something else like [JSONSTOREPLUS], o= r replace the original?

- chris---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@w= ebdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: suppo= rt@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 --000000000000a8dfdf05a5335138-- . Tom Duke

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:

LineItem variable set (2007) Getting Total Quantity (1997) Emailer Set Up (1997) code to phantom spacing (2001) and more [shipcost].... (2001) case number with spaces. (2000) [WebDNA] WebDNA staging server (2008) Calculating multiple shipping... (1997) snicker, snicker (1997) NT Version on IIS 4.0 (1997) WCS Newbie question (1997) Shipping Costs Not Updating When Adding Items (1997) Help name our technology! (1997) Slow NT mail. (2000) WebMerchant 3.0 for Mac shipping now (1998) More on [purchase] (1998) Newbie problem blah blah blah (1997) Emailer port change (1997) Date search and sendmail (1997) Merchant account (1998)