Is it difficult to make db_postgres and/or sqlops support no values returned - i.e. a void result set?
Recent versions of Postgres allow stored procedures to return 'void'. I like to call these a lot, but unfortunately sqlops or the database layer does not like that. So, I have to either write wrappers or make the procedures return things like a boolean 't' just to fix this.
On Sunday 10 October 2010, Alex Balashov wrote:
Is it difficult to make db_postgres and/or sqlops support no values returned - i.e. a void result set?
Recent versions of Postgres allow stored procedures to return 'void'. I like to call these a lot, but unfortunately sqlops or the database layer does not like that. So, I have to either write wrappers or make the procedures return things like a boolean 't' just to fix this.
Hi Alex,
i assume that you refer to the version 1 of the internal DB API, as you mentioned sqlops. Maybe the internal function of postgres return some status that previously were only emitted in an error condition.
Can you share some more details what exactly is not working for you? Do you get an error message or something like this?
Viele Grüße,
Henning
Is sqlops pegged to a version of the DB API considered obsolete?
Should I be worried? I'm an extremely heavy user of sqlops,
-- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/
On Oct 11, 2010, at 11:13 AM, Henning Westerholt <henning.westerholt@1und1.de
wrote:
On Sunday 10 October 2010, Alex Balashov wrote:
Is it difficult to make db_postgres and/or sqlops support no values returned - i.e. a void result set?
Recent versions of Postgres allow stored procedures to return 'void'. I like to call these a lot, but unfortunately sqlops or the database layer does not like that. So, I have to either write wrappers or make the procedures return things like a boolean 't' just to fix this.
Hi Alex,
i assume that you refer to the version 1 of the internal DB API, as you mentioned sqlops. Maybe the internal function of postgres return some status that previously were only emitted in an error condition.
Can you share some more details what exactly is not working for you? Do you get an error message or something like this?
Viele Grüße,
Henning
On Monday 11 October 2010, Alex Balashov wrote:
Is sqlops pegged to a version of the DB API considered obsolete?
Should I be worried? I'm an extremely heavy user of sqlops,
Hi Alex,
no, its all fine. :-) Its just that i wanted to make sure before going into details if its the API that i know somewhat, or the one that Andrei and others have more knowledge in.
Cheers,
Henning
On 10/11/10 5:46 PM, Alex Balashov wrote:
Is sqlops pegged to a version of the DB API considered obsolete?
No, v1 of DB API is the one coming from kamailio, based on ser 0.9.x. All K modules uses it.
v2 is from ser 2.x, with a different concept behind, most important addition imo is prepared statements support. A transition from v1 to v2 will be seamless for config file. First the db drivers need to support v2, now not all of them do. Once that, I expect some modules will start to follow it, but will take time.
Should I be worried? I'm an extremely heavy user of sqlops,
:-) no worry, besides everything, it is open source, but anyhow I guess your next postgres plugin is to run kamailio config file embedded, or the other way around.
Back on track, sqlops is one of the fundamental modules for many of us these days.
Cheers, Daniel
-- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/
On Oct 11, 2010, at 11:13 AM, Henning Westerholt henning.westerholt@1und1.de wrote:
On Sunday 10 October 2010, Alex Balashov wrote:
Is it difficult to make db_postgres and/or sqlops support no values returned - i.e. a void result set?
Recent versions of Postgres allow stored procedures to return 'void'. I like to call these a lot, but unfortunately sqlops or the database layer does not like that. So, I have to either write wrappers or make the procedures return things like a boolean 't' just to fix this.
Hi Alex,
i assume that you refer to the version 1 of the internal DB API, as you mentioned sqlops. Maybe the internal function of postgres return some status that previously were only emitted in an error condition.
Can you share some more details what exactly is not working for you? Do you get an error message or something like this?
Viele Grüße,
Henning
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt