> On Sep 12, 2017, at 5:48 PM, David Adams via 4D_Tech <[email protected]> > wrote: > > Exciting stuff. I've read a ton about it and done some tests. Rob's plugin > doesn't have an explicit command for transferring object fields, but you > can stringify them and send them as text.
Most Postgres client libraries use text rather than binary encoding because the binary formats are not documented. Of course, you have the source but that is a lot of work :). But the binary option is especially fast and useful when you are sending/receiving binary, aka Postgres bytea. https://stackoverflow.com/questions/35600070/postgres-jsonb-specification-for-copy-in-binary-format > If you have exotic searching requirements, Postgres has a ton of > engine-level features...and a common add-on gives you a bunch of fuzzy > matching tools. I was talking with John DeSoi the other day and he says > that the fuzzy tools add-on includes "tri-grams". That's "n-grams" or > "q-grams" with a length of 3. I've got a stack of research papers on why > trigrams are so frickin amazing at fuzzy matching. I've tried (and failed) > to implement them effectively in 4D a couple of times. WIth Postgres, you > just add the fuzzy tools and away you go. Here are a couple of links if anyone is interested. https://www.postgresql.org/docs/9.6/static/pgtrgm.html https://www.postgresql.org/docs/9.6/static/textsearch.html John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
