Re: [GENERAL] New wrapper library: QUINCE
On 20/08/2014 3:51 AM, John R Pierce wrote: really well designed method of generating really awful nested queries?whatever. Sure, if that's what you're into. As the doco says: How far you go in the direction of monster queries is up to you, the application designer. Quince has no opinion, but whatever you decide, quince allows you to express your choice in manageable C++. (quince-lib.com/queries_in_c_expressions/rise_of_the_monster_query.html) Cheers, --- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] New wrapper library: QUINCE
Hi PostgreSQLers, I've released an open-source library called quince (QUeries In C++ Expressions) that helps you access PostgreSQL from C++. I know, I know: you've got plenty of those already, but this one is different ... It's an EDSL (Embedded Domain-Specific Language), which lets you build sophisticated SQL queries in C++ syntax with C++ data types, and it's also an ORM, which figures out how to represent your C++ structs/classes/tuples as multiple columns. It's a plain old library, so no special compiler and no code generation step. And fwiw it works with sqlite too (and maybe other DBMSes in the future -- it's a matter of adding backend libraries). It's all explained at http://quince-lib.com . Cheers, --- Michael Shepanski -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] index row requires 10040 bytes, maximum size is 8191
Craig Ringer writes: > >Thoughts, folks? Does this matter in practice, since anything you'd > want to index will in practice be small enough or a candidate for > full-text indexing? Here's my case: the field is meant to hold a person's name, so it's usually well under the 8191-byte limit. I want it indexed so that I can sort on it quickly. I also want it to be robust against abuse, so if someone does enter the text of _War and Peace_ as their name, I want to handle that gracefully. I can achieve that by my own programming, outside of postgresql, and that's fine if I'm the only one who has gotten into this fix. Otoh if it's a common problem then there's a reason why removing the limitation might matter in practice. Regards, --- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
