Derek, the conventional wisdom is connecting to a db is expensive.
I'm willing to be convinced, but I need some data. Can you point me to some?
Because if your statement is true, we could eliminate some pretty hairy
code in the DAL to support pooling.
On Wednesday, March 19, 2014 7:44:10 PM UTC-4, Derek wrote:
>
> I'd say the answer to 2 is 'not really'. Believe it or not, opening and
> dropping database connections is a fast operation.
>
> On Tuesday, March 18, 2014 11:33:04 PM UTC-7, tec...@gmail.com wrote:
>>
>> Dear Sirs,
>>
>>
>> I understand it's possible to use databases without DAL.
>> For example function in controller:
>>
>> def values():
>> client = pymongo.MongoClient('localhost', 27017)
>> db = client.mybase
>> mytable = db["mytable"]
>> res = mytable.find()
>> .....
>>
>> return dict(....)
>>
>> And of course it works.
>> But is it fast to connect/disconnect every time in function? What's about
>> connection pool?
>> I consider connection pool could increase access to database.
>>
>> 1. Actually I would like to ask how to access to database without DAL but
>> at maximum speed?
>> 2. Do I need connection pool for fast database access? (I think, yes.)
>> 3. How could I build custom connection pool for database access without
>> DAL? Or any solution to re-use connections to database server? Any examples?
>>
>>
>>
>> Andrey A.
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
