11 Oct
2010
11 Oct
'10
6:46 p.m.
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(a)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