On Nov 30, 2010, at 2:59 AM, Gennady Kushnir wrote:
> Thank you for these tips
>
> The point is that I do use multiple EOF stacks. I clearly admit that
> each EOObjectStoreCoordinator gets its own set of db connections.
It only needs a single connection to work.
>>>
>>> Let's
Thank you for these tips
The point is that I do use multiple EOF stacks. I clearly admit that
each EOObjectStoreCoordinator gets its own set of db connections.
>>>
>>> It only needs a single connection to work.
>>
>> Let's say single connection for each used database ;)
>> In fact that i
On Nov 24, 2010, at 2:18 AM, Gennady Kushnir wrote:
>>> The point is that I do use multiple EOF stacks. I clearly admit that
>>> each EOObjectStoreCoordinator gets its own set of db connections.
>>
>> It only needs a single connection to work.
>
> Let's say single connection for each used datab
>> The point is that I do use multiple EOF stacks. I clearly admit that
>> each EOObjectStoreCoordinator gets its own set of db connections.
>
> It only needs a single connection to work.
Let's say single connection for each used database ;)
In fact that is a goal I'd like to achieve to have a sin
On Nov 23, 2010, at 3:01 PM, Gennady Kushnir wrote:
> Hello all
> Thanks for you replies. Looks like I have enough to explore yet.
>
>> It should not be creating more unless you are creating more EOF stacks in
>> you code.
>
> The point is that I do use multiple EOF stacks. I clearly admit tha
Hello all
Thanks for you replies. Looks like I have enough to explore yet.
> It should not be creating more unless you are creating more EOF stacks in you
> code.
The point is that I do use multiple EOF stacks. I clearly admit that
each EOObjectStoreCoordinator gets its own set of db connections
Hi Guys;
One per db context and no.
My problem is that I see my app opening more connections than a number
of models it has.
Mike talked through a work-around for this bug to me recently on here.
I had the same problem eating lots of connections into an Oracle
database from the app-servers.
Hi,
On Nov 23, 2010, at 1:54 AM, Gennady Kushnir wrote:
> Hello Chuck and others.
> I'd like ask some more questions )
>
> 2010/8/27 Chuck Hill :
>>
>> On Aug 25, 2010, at 11:10 PM, Dov Rosenberg wrote:
>>
>>> I am revisiting some old EOF documentation and wanted to make sure I
>>> understood
Hi,
you can use the following to check who is creating your channels:
public Application()
{
super();
...
// register for database channel needed notification
NSNotificationCenter.defaultCenter().addObserver(this,
new NSSelector("createAdditionalDatabaseChannel", new Cla
Hello Gennady,
> Hello Chuck and others.
> I'd like ask some more questions )
>
> 2010/8/27 Chuck Hill :
>>
>> On Aug 25, 2010, at 11:10 PM, Dov Rosenberg wrote:
>>
>>> I am revisiting some old EOF documentation and wanted to make sure I
>>> understood a few things. Are the following statement
Hello Chuck and others.
I'd like ask some more questions )
2010/8/27 Chuck Hill :
>
> On Aug 25, 2010, at 11:10 PM, Dov Rosenberg wrote:
>
>> I am revisiting some old EOF documentation and wanted to make sure I
>> understood a few things. Are the following statements true?
>>
>>
>> * When an EO
On Aug 25, 2010, at 11:10 PM, Dov Rosenberg wrote:
> I am revisiting some old EOF documentation and wanted to make sure I
> understood a few things. Are the following statements true?
>
>
> * When an EOModel is found and connected to a database when the app starts
> up each database connect
I am revisiting some old EOF documentation and wanted to make sure I understood
a few things. Are the following statements true?
* When an EOModel is found and connected to a database when the app starts
up each database connection is mapped to an EODatabaseChannel?
* A single EOObjectSto
13 matches
Mail list logo
