Bug #415575 “pointer to propoas system” : Bugs : web2-Conf

Revision history for this message

yarko (yarkot) wrote on 2009-08-18:

#1

NOTE TO SELF: Doug reports psycopg2 crashes if 2 cursors active (to 2 db's) - test; regardless, commit and act in one db at a time in any read-only ref to a django db (should you do that).

Revision history for this message

Massimo (mdipierro) wrote on 2009-08-18: Re: [Bug 415575] Re: pointer to propoas system

#2

web2py only opens one cursor per connection and there is only one db.
Can you explain the problem?

On Aug 18, 2009, at 3:21 PM, yarko wrote:

> NOTE TO SELF: Doug reports psycopg2 crashes if 2 cursors active (to 2
> db's) - test; regardless, commit and act in one db at a time in any
> read-only ref to a django db (should you do that).
>
> --
> pointer to propoas system
> https://bugs.launchpad.net/bugs/415575
> You received this bug notification because you are a member of
> Web2Conf
> Core Team, which is the registrant for web2-Conf.
>
> Status in Conference Planning & Registration System: New
>
> Bug description:
> feature request:
>
> add a pointer to the proposal system.
>
> No clue what the value should be, that's an implementation detail
> that depends on what makes sense.
>
> ideas: e-mail, user name, primary key
>
> How this is populated is another implementation detail.

Revision history for this message

yarko (yarkot) wrote on 2009-08-18:

#3

the discussion on pycon list from Doug was that psycogp2 has issues w/ 2
cursors;
I mentioned that opening 2 db's w/ web2py should not be a problem;

I made a note, in case psycogp2 has issues - am going to test reading
presenter, and user database from django side...
not sure how I will use yet - first want to see that I can see the user
table (and if needed either use it, or copy it when someone tries to log
in).

Secondary is logging if they are presenter (or pointing to their record on
the django side) --- all speculative at this point....

On Tue, Aug 18, 2009 at 3:38 PM, Massimo <email address hidden> wrote:

> web2py only opens one cursor per connection and there is only one db.
> Can you explain the problem?
>
> On Aug 18, 2009, at 3:21 PM, yarko wrote:
>
> > NOTE TO SELF: Doug reports psycopg2 crashes if 2 cursors active (to 2
> > db's) - test; regardless, commit and act in one db at a time in any
> > read-only ref to a django db (should you do that).
> >
> > --
> > pointer to propoas system
> > https://bugs.launchpad.net/bugs/415575
> > You received this bug notification because you are a member of
> > Web2Conf
> > Core Team, which is the registrant for web2-Conf.
> >
> > Status in Conference Planning & Registration System: New
> >
> > Bug description:
> > feature request:
> >
> > add a pointer to the proposal system.
> >
> > No clue what the value should be, that's an implementation detail
> > that depends on what makes sense.
> >
> > ideas: e-mail, user name, primary key
> >
> > How this is populated is another implementation detail.
>
> --
> pointer to propoas system
> https://bugs.launchpad.net/bugs/415575
> You received this bug notification because you are a member of Web2Conf
> Core Team, which is the registrant for web2-Conf.
>
> Status in Conference Planning & Registration System: New
>
> Bug description:
> feature request:
>
> add a pointer to the proposal system.
>
> No clue what the value should be, that's an implementation detail that
> depends on what makes sense.
>
> ideas: e-mail, user name, primary key
>
> How this is populated is another implementation detail.
>

the discussion on pycon list from Doug was that psycogp2 has issues w/ 2
cursors;
I mentioned that opening 2 db's w/ web2py should not be a problem;

I made a note, in case psycogp2 has issues - am going to test reading
presenter, and user database from django side...
not sure how I will use yet - first want to see that I can see the user
table (and if needed either use it, or copy it when someone tries to log
in).

Secondary is  logging if they are presenter (or pointing to their record on
the django side) --- all speculative at this point....

On Tue, Aug 18, 2009 at 3:38 PM, Massimo <mdipierro@cs.depaul.edu> wrote:

> web2py only opens one cursor per connection and there is only one db.
> Can you explain the problem?
>
> On Aug 18, 2009, at 3:21 PM, yarko wrote:
>
> > NOTE TO SELF:  Doug reports psycopg2 crashes if 2 cursors active (to 2
> > db's) - test; regardless, commit and act in one db at a time in any
> > read-only ref to a django db (should you do that).
> >
> > --
> > pointer to propoas system
> > https://bugs.launchpad.net/bugs/415575
> > You received this bug notification because you are a member of
> > Web2Conf
> > Core Team, which is the registrant for web2-Conf.
> >
> > Status in Conference Planning & Registration System: New
> >
> > Bug description:
> > feature request:
> >
> > add a pointer to the proposal system.
> >
> > No clue what the value should be, that's an implementation detail
> > that depends on what makes sense.
> >
> > ideas: e-mail, user name, primary key
> >
> > How this is populated is another implementation detail.
>
> --
> pointer to propoas system
> https://bugs.launchpad.net/bugs/415575
> You received this bug notification because you are a member of Web2Conf
> Core Team, which is the registrant for web2-Conf.
>
> Status in Conference Planning & Registration System: New
>
> Bug description:
> feature request:
>
> add a pointer to the proposal system.
>
> No clue what the value should be, that's an implementation detail that
> depends on what makes sense.
>
> ideas: e-mail, user name, primary key
>
> How this is populated is another implementation detail.
>

Revision history for this message

Massimo (mdipierro) wrote on 2009-08-18:

#4

I use psycopg2 a lot and never has an issue. I can see why having two
cursors within the same connection may be a problem. That should not
happen and it does not happen with web2py. I am sure there is no issue
with one cursor per connection and multiple concurrent connections,
which is what we do. Anyway, feel free to test it.

On Aug 18, 2009, at 4:14 PM, yarko wrote:

> the discussion on pycon list from Doug was that psycogp2 has issues
> w/ 2
> cursors;
> I mentioned that opening 2 db's w/ web2py should not be a problem;
>
> I made a note, in case psycogp2 has issues - am going to test reading
> presenter, and user database from django side...
> not sure how I will use yet - first want to see that I can see the
> user
> table (and if needed either use it, or copy it when someone tries to
> log
> in).
>
> Secondary is logging if they are presenter (or pointing to their
> record on
> the django side) --- all speculative at this point....
>
> On Tue, Aug 18, 2009 at 3:38 PM, Massimo <email address hidden>
> wrote:
>
>> web2py only opens one cursor per connection and there is only one db.
>> Can you explain the problem?
>>
>> On Aug 18, 2009, at 3:21 PM, yarko wrote:
>>
>>> NOTE TO SELF: Doug reports psycopg2 crashes if 2 cursors active
>>> (to 2
>>> db's) - test; regardless, commit and act in one db at a time in any
>>> read-only ref to a django db (should you do that).
>>>
>>> --
>>> pointer to propoas system
>>> https://bugs.launchpad.net/bugs/415575
>>> You received this bug notification because you are a member of
>>> Web2Conf
>>> Core Team, which is the registrant for web2-Conf.
>>>
>>> Status in Conference Planning & Registration System: New
>>>
>>> Bug description:
>>> feature request:
>>>
>>> add a pointer to the proposal system.
>>>
>>> No clue what the value should be, that's an implementation detail
>>> that depends on what makes sense.
>>>
>>> ideas: e-mail, user name, primary key
>>>
>>> How this is populated is another implementation detail.
>>
>> --
>> pointer to propoas system
>> https://bugs.launchpad.net/bugs/415575
>> You received this bug notification because you are a member of
>> Web2Conf
>> Core Team, which is the registrant for web2-Conf.
>>
>> Status in Conference Planning & Registration System: New
>>
>> Bug description:
>> feature request:
>>
>> add a pointer to the proposal system.
>>
>> No clue what the value should be, that's an implementation detail
>> that
>> depends on what makes sense.
>>
>> ideas: e-mail, user name, primary key
>>
>> How this is populated is another implementation detail.
>>
>
> --
> pointer to propoas system
> https://bugs.launchpad.net/bugs/415575
> You received this bug notification because you are a member of
> Web2Conf
> Core Team, which is the registrant for web2-Conf.
>
> Status in Conference Planning & Registration System: New
>
> Bug description:
> feature request:
>
> add a pointer to the proposal system.
>
> No clue what the value should be, that's an implementation detail
> that depends on what makes sense.
>
> ideas: e-mail, user name, primary key
>
> How this is populated is another implementation detail.

I use psycopg2 a lot and never has an issue. I can see why having two  
cursors within the same connection may be a problem. That should not  
happen and it does not happen with web2py. I am sure there is no issue  
with one cursor per connection and multiple concurrent connections,  
which is what we do. Anyway, feel free to test it.

On Aug 18, 2009, at 4:14 PM, yarko wrote:

> the discussion on pycon list from Doug was that psycogp2 has issues  
> w/ 2
> cursors;
> I mentioned that opening 2 db's w/ web2py should not be a problem;
>
> I made a note, in case psycogp2 has issues - am going to test reading
> presenter, and user database from django side...
> not sure how I will use yet - first want to see that I can see the  
> user
> table (and if needed either use it, or copy it when someone tries to  
> log
> in).
>
> Secondary is  logging if they are presenter (or pointing to their  
> record on
> the django side) --- all speculative at this point....
>
> On Tue, Aug 18, 2009 at 3:38 PM, Massimo <mdipierro@cs.depaul.edu>
> wrote:
>
>> web2py only opens one cursor per connection and there is only one db.
>> Can you explain the problem?
>>
>> On Aug 18, 2009, at 3:21 PM, yarko wrote:
>>
>>> NOTE TO SELF:  Doug reports psycopg2 crashes if 2 cursors active  
>>> (to 2
>>> db's) - test; regardless, commit and act in one db at a time in any
>>> read-only ref to a django db (should you do that).
>>>
>>> --
>>> pointer to propoas system
>>> https://bugs.launchpad.net/bugs/415575
>>> You received this bug notification because you are a member of
>>> Web2Conf
>>> Core Team, which is the registrant for web2-Conf.
>>>
>>> Status in Conference Planning & Registration System: New
>>>
>>> Bug description:
>>> feature request:
>>>
>>> add a pointer to the proposal system.
>>>
>>> No clue what the value should be, that's an implementation detail
>>> that depends on what makes sense.
>>>
>>> ideas: e-mail, user name, primary key
>>>
>>> How this is populated is another implementation detail.
>>
>> --
>> pointer to propoas system
>> https://bugs.launchpad.net/bugs/415575
>> You received this bug notification because you are a member of  
>> Web2Conf
>> Core Team, which is the registrant for web2-Conf.
>>
>> Status in Conference Planning & Registration System: New
>>
>> Bug description:
>> feature request:
>>
>> add a pointer to the proposal system.
>>
>> No clue what the value should be, that's an implementation detail  
>> that
>> depends on what makes sense.
>>
>> ideas: e-mail, user name, primary key
>>
>> How this is populated is another implementation detail.
>>
>
> -- 
> pointer to propoas system
> https://bugs.launchpad.net/bugs/415575
> You received this bug notification because you are a member of  
> Web2Conf
> Core Team, which is the registrant for web2-Conf.
>
> Status in Conference Planning & Registration System: New
>
> Bug description:
> feature request:
>
> add a pointer to the proposal system.
>
> No clue what the value should be, that's an implementation detail  
> that depends on what makes sense.
>
> ideas: e-mail, user name, primary key
>
> How this is populated is another implementation detail.

Revision history for this message

Carl Karsten (carlfk) wrote on 2017-04-10:

#5

old bug, don't care any more.

Changed in web2conf:
status:	New → Won't Fix

web2-Conf

pointer to propoas system

Bug Description

Other bug subscribers

Remote bug watches