Re: [racket-users] JSON vs. normal Racket for simple serialization to database
In this particular case, the only purpose is saving/loading data to/from a db column. I have plenty of other uses for JSON, so I'm thankful for the Racket JSON library, but I lean toward simplicity when possible. On Wednesday, December 12, 2018 at 10:35:24 AM UTC-5, Jon Zeppieri wrote: > > Postgres can index jsonb column data. Also, other languages will have an > easier time reading it. If neither of those matter for your case, then no. > > - Jon > > > On Wed, Dec 12, 2018 at 10:26 AM Brian Adkins > wrote: > >> I have some simple serialization needs. In Ruby, I would always serialize >> an object to JSON and store in a postgres text column. However, w/ Racket, >> it appears another option is to simply use read/write. Any reason not to >> use read/write for serialization instead of JSON? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket-users...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] JSON vs. normal Racket for simple serialization to database
Postgres can index jsonb column data. Also, other languages will have an easier time reading it. If neither of those matter for your case, then no. - Jon On Wed, Dec 12, 2018 at 10:26 AM Brian Adkins wrote: > I have some simple serialization needs. In Ruby, I would always serialize > an object to JSON and store in a postgres text column. However, w/ Racket, > it appears another option is to simply use read/write. Any reason not to > use read/write for serialization instead of JSON? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[racket-users] JSON vs. normal Racket for simple serialization to database
I have some simple serialization needs. In Ruby, I would always serialize an object to JSON and store in a postgres text column. However, w/ Racket, it appears another option is to simply use read/write. Any reason not to use read/write for serialization instead of JSON? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
