Well, that has the C library support mixed in with a ton of other stuff.
What's really needed is a "library" (or whatever the rust term is) that
provides the same functionality that [1] and [2] provide at the C level
today. Ideally the Postgres project would support that since it involves
C
Rather have look at https://github.com/posix4e/jsoncdc
On 01-Aug-2016 1:16 am, "Jim Nasby" wrote:
> On 7/30/16 1:08 AM, Priya Ranjan wrote:
>
>> Thanks Greg, but not as a binding but a substitute for C++ code, as this
>> code is untrusted there could be an exception
On 7/30/16 1:08 AM, Priya Ranjan wrote:
Thanks Greg, but not as a binding but a substitute for C++ code, as this
code is untrusted there could be an exception bringing down the entire
server. Rustlang guarantees memory safety.
https://github.com/thehydroimpulse/postgres-extension.rs appears to
Thanks Greg, but not as a binding but a substitute for C++ code, as this
code is untrusted there could be an exception bringing down the entire
server. Rustlang guarantees memory safety.
Regards
On Sat, 30 Jul 2016 11:09 Greg Chase wrote:
> Hi Rangan,
> Its nice to hear
Hi Rangan,
Its nice to hear from you.
I'll let other folks of the community speak about language bindings. But,
and important thing to understand about MADlib in its current capabilities
is that it is developed to work in-database in a variety of
PostgreSQL-derived database platforms. To date, we
Thanks for posting, Greg. It was an interesting discussion.
Frank
On Wed, Jul 27, 2016 at 6:50 PM, Gregory Chase wrote:
> Today's open office hours call turned into a delightful discussion with a
> new user to MADlib. Other new users to MADlib may appreciate his
>
Today's open office hours call turned into a delightful discussion with a
new user to MADlib. Other new users to MADlib may appreciate his questions.
Here's the full replay:
https://youtu.be/EPQk5Uzs8OY?t=35s
Here's the topics we talked about:
0:35 Our new users’ use case