Bug 138071

When I try to attach to the bug after it is filed ...

Software error:

DBD::Pg::st execute failed: ERROR:  attachments_attach_id_seq.currval is not yet
defined in this session [for Statement "SELECT
currval('attachments_attach_id_seq')"] at Bugzilla/DBcompat.pm line 112
	Bugzilla::DBcompat::LastKey('attachments','attach_id') called at
/var/www/bugzilla/beta2/attachment.cgi line 888
	main::insert('\x{89}PNG\x{d}\x{a}\x{1a}\x{a}\x{0}\x{0}\x{0}\x{d}IHDR\x{0}\x{0}\x{4}\x{0}\x{0}\x{0}\x{3}\x{0}\x{8}\x{2}\x{0}\x{0}\x{0}5\x{d8}\x{82}Z\x{0}\x{0}\x{0}\x{3}sBIT\x{8}\x{8}\x{8}\x{db}\x{e1}O\x{e0}\x{0}\x{0}
\x{0}IDATx\x{9c}\x{ec}\x{bd}_...') called at
/var/www/bugzilla/beta2/attachment.cgi line 125

For help, please send mail to the webmaster (bugzilla

Need to have fixed by beta3

(In reply to comment #0)
> Trying to create a new bug, with an attachment I get the following software error:
> 
> Software error:
> 
> DBD::Pg::st execute failed: ERROR:  attachments_attach_id_seq.currval is not yet
> defined in this session [for Statement "SELECT
> currval('attachments_attach_id_seq')"] at Bugzilla/DBcompat.pm line 112
> 	Bugzilla::DBcompat::LastKey('attachments','attach_id') called at
> /var/www/bugzilla/beta2/post_bug.cgi line 678
> 
> For help, please send mail to the webmaster (bugzilla), giving this
> error message and the time and date of the error.


If you visit this bug did the attachment actually get added to the new bug? What
is the bug number?

Found the reason for the error message, strange how it doesnt happen all the
time.  Somehow the session is ending before the get last id key is being called.

Explanation:

You attempted to execute <sequence name>.CURRVAL before using <sequence
name>.NEXTVAL in the current session.

User Action:

Execute <sequence name>.NEXTVAL before executing <sequence name>.CURRVAL

Ping

did you change anything?  It seems to have worked when I tried this yesterday
(or day before).

I have changed the way LastKey() behaves which may help with this since it was
working in differnt section of code instead of the same db handle that was in
post_bug.cgi. So we will close this and reopen if you see it again.