Re: GSoC 2018: thrift encoding format

Поиск
Список
Период
Сортировка
Искать
От
Aleksander Alekseev
Тема
Re: GSoC 2018: thrift encoding format
Дата
в 12:39:15
Msg-id
20180503093914.GA27569@e733.localdomain
Ответ на
Список
Дерево обсуждения
GSoC 2018: thrift encoding format Charles Cui <charles.cui1984@gmail.com>
Re: GSoC 2018: thrift encoding format Aleksander Alekseev <a.alekseev@postgrespro.ru>
Re: GSoC 2018: thrift encoding format Charles Cui <charles.cui1984@gmail.com>
Re: GSoC 2018: thrift encoding format Aleksander Alekseev <a.alekseev@postgrespro.ru>
Re: GSoC 2018: thrift encoding format Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Re: GSoC 2018: thrift encoding format Aleksander Alekseev <a.alekseev@postgrespro.ru>
Re: GSoC 2018: thrift encoding format Stephen Frost <sfrost@snowman.net>
Re: GSoC 2018: thrift encoding format Aleksander Alekseev <a.alekseev@postgrespro.ru>
Re: GSoC 2018: thrift encoding format Stephen Frost <sfrost@snowman.net>
Re: GSoC 2018: thrift encoding format Charles Cui <charles.cui1984@gmail.com>
Re: GSoC 2018: thrift encoding format Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Re: GSoC 2018: thrift encoding format Aleksander Alekseev <a.alekseev@postgrespro.ru>
Hello Charles,

> Thanks for your confirm Aleksander!
> Also I am thinking of how to deal with complex
> data structure like map, list, or set. I guess one possible
> solution is to get raw data bytes for these data structure?
> Otherwise it could be hard to wrap into a Datum.

Personally I think raw data bytes are OK if functions for getting all
keys and values from this data are provided. Another possibility is just
converting Thrift to JSONB and vise versa. In this case only two
procedures are required and all the rest is available out-of-the-box.

-- 
Best regards,
Aleksander Alekseev
В списке pgsql-hackers по дате отправления
От: Craig Ringer
Дата:
От: Andrey Borodin
Дата:
Сообщение: Re: GSOC 2018
FAQ