[Mono-list] Npgsql problem "create local temporary"

Francisco Figueiredo Jr. fxjrlists@yahoo.com.br
Thu, 17 Jun 2004 11:14:36 -0300 (ART)

--- donaldi sp <don_aldi@yahoo.com> escreveu: 
> Hi Frans,

Hi Donaldi.

> yes, when I add "Polling=false" in connection string,
> it's look fine, but can you give an explaination
> between using pooling and not using it, what's the
> benefit and the cost of that thing, at least you can
> give me a link about that.

The cost of it is the load of typemappings as well as initial connection setup,
like authentication, encoding that you won't have when using cache.

This can be heavy if you have a lot of open close statements in your code.

The drawback can be problems like yours where you can't get some consistent
behavior dependent on connection close, as the connection won't be closed until
you terminate your application. (Connection close after some timeout will be
implemented yet.)

I think that as long as you don't depends on connection close you should stay
with connection pooling.

> but I got error like "Npgsql.NpgsqlException: cache
> lookup failed for relation 21036" when I browse again
> the page that have error before.

Uhmmmmm, could you provide me a simple test case?
Also, if possible, post a bug in mono bugzilla (http://bugzilla.ximian.com)
and/or gborg (http://gborg.postgresql.org/project/npgsql/bugs/buglist.php).

Thanks in advance.


Francisco Figueiredo Jr.


Participe da pesquisa global sobre o Yahoo! Mail: