record locking fails. postgresql 8.2.4

View: New views
4 Messages — Rating Filter:   Alert me  

record locking fails. postgresql 8.2.4

by Julian-27 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

Just a simple table using postgresql 8.2.4
id PK
txt1 text
I actually created this table within rekall.
the form has one field (txt1), a save button and record locking enabled.
1.On form launch.
The form shows "Unlocked" in the status bar.
2.I attempt to enter data into the field and get Warning "Transaction already
in progress", "Record Locked" in the status bar.
3.Close form.

1.LOG:  statement: select lock_test.id, txt1 from lock_test
2.LOG:  statement: begin
3.LOG:  statement: rollback

I don't see any "select ... for update "
Mike have you tested record locking rekall with postgres 8.2?
I actually haven't tested locking with 7.4 either, if anyone has record
locking working with any version of postgresql please comment.
Jules
_______________________________________________
Rekall mailing list
Rekall@...
http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall

Re: record locking fails. postgresql 8.2.4

by Andree Clausing :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Rekall Release 2.4.3 cvs is the only version where record locking with
Postgres 8.2 is working.

All other versions (Rekall-2.4.5, Rekall-2.4.6) record locking doesn't
work.

Andree


Am 11.12.2007, 07:38 Uhr, schrieb Julian <tempura@...>:

> Hi,
>
> Just a simple table using postgresql 8.2.4
> id PK
> txt1 text
> I actually created this table within rekall.
> the form has one field (txt1), a save button and record locking enabled.
> 1.On form launch.
> The form shows "Unlocked" in the status bar.
> 2.I attempt to enter data into the field and get Warning "Transaction  
> already
> in progress", "Record Locked" in the status bar.
> 3.Close form.
>
> 1.LOG:  statement: select lock_test.id, txt1 from lock_test
> 2.LOG:  statement: begin
> 3.LOG:  statement: rollback
>
> I don't see any "select ... for update "
> Mike have you tested record locking rekall with postgres 8.2?
> I actually haven't tested locking with 7.4 either, if anyone has record
> locking working with any version of postgresql please comment.
> Jules
> _______________________________________________
> Rekall mailing list
> Rekall@...
> http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall


_______________________________________________
Rekall mailing list
Rekall@...
http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall

Re: record locking fails. postgresql 8.2.4

by Julian-27 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm trying to verify this, but my 2.4.3 build has python issues. it builds
with it..but can't find it runtime..go figure.
I did a diff on /db/pgsql/ but theres only 2 extra lines in kb_pgsql.cpp
(rekall 2.4.6).I doubt they are the cause. (limits and offsets)
I was hoping to get a patch together, but i'm not going mess about on this
because i really don't know where else to look (in the source).
Jules
On Fri, 14 Dec 2007, Andree Clausing wrote:

> Rekall Release 2.4.3 cvs is the only version where record locking with
> Postgres 8.2 is working.
>
> All other versions (Rekall-2.4.5, Rekall-2.4.6) record locking doesn't
> work.
>
> Andree
>
> Am 11.12.2007, 07:38 Uhr, schrieb Julian <tempura@...>:
> > Hi,
> >
> > Just a simple table using postgresql 8.2.4
> > id PK
> > txt1 text
> > I actually created this table within rekall.
> > the form has one field (txt1), a save button and record locking enabled.
> > 1.On form launch.
> > The form shows "Unlocked" in the status bar.
> > 2.I attempt to enter data into the field and get Warning "Transaction
> > already
> > in progress", "Record Locked" in the status bar.
> > 3.Close form.
> >
> > 1.LOG:  statement: select lock_test.id, txt1 from lock_test
> > 2.LOG:  statement: begin
> > 3.LOG:  statement: rollback
> >
> > I don't see any "select ... for update "
> > Mike have you tested record locking rekall with postgres 8.2?
> > I actually haven't tested locking with 7.4 either, if anyone has record
> > locking working with any version of postgresql please comment.
> > Jules
> > _______________________________________________
> > Rekall mailing list
> > Rekall@...
> > http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall
>
> _______________________________________________
> Rekall mailing list
> Rekall@...
> http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall

_______________________________________________
Rekall mailing list
Rekall@...
http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall

Re: record locking fails. postgresql 8.2.4

by Andree Clausing :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I use ActivePython 2.3.5 Build 236 on windows, but I can compile
it on kanotix (debian) too if you wish.

Andree

Am 15.12.2007, 13:09 Uhr, schrieb Julian <tempura@...>:

> I'm trying to verify this, but my 2.4.3 build has python issues. it  
> builds
> with it..but can't find it runtime..go figure.
> I did a diff on /db/pgsql/ but theres only 2 extra lines in kb_pgsql.cpp
> (rekall 2.4.6).I doubt they are the cause. (limits and offsets)
> I was hoping to get a patch together, but i'm not going mess about on  
> this
> because i really don't know where else to look (in the source).
> Jules
> On Fri, 14 Dec 2007, Andree Clausing wrote:
>> Rekall Release 2.4.3 cvs is the only version where record locking with
>> Postgres 8.2 is working.
>>
>> All other versions (Rekall-2.4.5, Rekall-2.4.6) record locking doesn't
>> work.
>>
>> Andree
>>
>> Am 11.12.2007, 07:38 Uhr, schrieb Julian <tempura@...>:
>> > Hi,
>> >
>> > Just a simple table using postgresql 8.2.4
>> > id PK
>> > txt1 text
>> > I actually created this table within rekall.
>> > the form has one field (txt1), a save button and record locking  
>> enabled.
>> > 1.On form launch.
>> > The form shows "Unlocked" in the status bar.
>> > 2.I attempt to enter data into the field and get Warning "Transaction
>> > already
>> > in progress", "Record Locked" in the status bar.
>> > 3.Close form.
>> >
>> > 1.LOG:  statement: select lock_test.id, txt1 from lock_test
>> > 2.LOG:  statement: begin
>> > 3.LOG:  statement: rollback
>> >
>> > I don't see any "select ... for update "
>> > Mike have you tested record locking rekall with postgres 8.2?
>> > I actually haven't tested locking with 7.4 either, if anyone has  
>> record
>> > locking working with any version of postgresql please comment.
>> > Jules
>> > _______________________________________________
>> > Rekall mailing list
>> > Rekall@...
>> > http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall
>>
>> _______________________________________________
>> Rekall mailing list
>> Rekall@...
>> http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall
>
> _______________________________________________
> Rekall mailing list
> Rekall@...
> http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall


_______________________________________________
Rekall mailing list
Rekall@...
http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall
LightInTheBox - Buy quality products at wholesale price