Re: dbpool problem

"Nikos Balkanas" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <F87836524E00476DB7339B021D350F7D@tardis>
No. There is no point in having a different pool/thread, otherwise it is a buffer, not a pool. When using the DB (insert, select, update, etc.) use gwlist_consume and when finished with the SQL return it with gwlist_append. Use a common pool for all threads.

If you need more help check source code.

Nikos
  ----- Original Message ----- 
  From: Esteban Cacavelos 
  To: Nikos Balkanas 
  Cc: devel Devel 
  Sent: Thursday, January 28, 2010 10:52 PM
  Subject: Re: dbpool problem


  Do you mean use gwlist_consume instead gwlist_get (in dbpool_check)  and  gwlist_append instead gwlist_produce (in dbpool_increase) ? 

  or to use directly to get connections  ?


  My SOLUTION (for the moment) is to hold one pool per thread and it works ;).


  -- 
  Esteban L. Cacavelos de Amoriza
  Cel: 0981 220 429
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.