Message boards : Number crunching : Old work still stuck in
Message board moderation

To post messages, you must log in.

AuthorMessage
Pete49

Send message
Joined: 18 Sep 04
Posts: 35
Credit: 250,303
RAC: 0
Message 8117 - Posted: 19 Jun 2005, 6:38:32 UTC
Last modified: 19 Jun 2005, 6:38:47 UTC

These go way back!

Is there anyway 0 credit can be manually granted just to clear these from my pending list.

http://lhcathome.cern.ch/result.php?resultid=167586
http://lhcathome.cern.ch/result.php?resultid=295028
http://lhcathome.cern.ch/result.php?resultid=472473
http://lhcathome.cern.ch/result.php?resultid=472869
http://lhcathome.cern.ch/result.php?resultid=472874


<img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83">
ID: 8117 · Report as offensive     Reply Quote
Kenneth Larsen

Send message
Joined: 2 Sep 04
Posts: 36
Credit: 90,806
RAC: 0
Message 8119 - Posted: 19 Jun 2005, 17:52:18 UTC

I have one as well:
http://lhcathome.cern.ch/result.php?resultid=295422
ID: 8119 · Report as offensive     Reply Quote
Profile sysfried

Send message
Joined: 27 Sep 04
Posts: 282
Credit: 1,415,417
RAC: 0
Message 8120 - Posted: 19 Jun 2005, 20:14:10 UTC - in response to Message 8119.  

> I have one as well:
> http://lhcathome.cern.ch/result.php?resultid=295422
>
go ahead, make my day.. I've got 17 still pending:
*snipp*
here's just one!
http://lhcathome.cern.ch/workunit.php?wuid=91991
*snipp*

*hoping that LeMans 24 was more fun than formula 1*

:-)
ID: 8120 · Report as offensive     Reply Quote
Profile Markku Degerholm

Send message
Joined: 3 Sep 04
Posts: 212
Credit: 4,545
RAC: 0
Message 8141 - Posted: 20 Jun 2005, 11:28:40 UTC

I invalidated these manually, I hope I got it right now (on the first try I crashed the whole database:( )

Markku Degerholm
LHC@home admin
ID: 8141 · Report as offensive     Reply Quote
Profile sysfried

Send message
Joined: 27 Sep 04
Posts: 282
Credit: 1,415,417
RAC: 0
Message 8143 - Posted: 20 Jun 2005, 12:54:12 UTC - in response to Message 8141.  

> I invalidated these manually, I hope I got it right now (on the first try I
> crashed the whole database:( )
>
>
:-O

be careful with your SQL "update" commands! ;-)
ID: 8143 · Report as offensive     Reply Quote
STE\/E

Send message
Joined: 2 Sep 04
Posts: 352
Credit: 1,393,150
RAC: 0
Message 8145 - Posted: 20 Jun 2005, 14:01:11 UTC - in response to Message 8141.  
Last modified: 20 Jun 2005, 14:01:29 UTC

> I invalidated these manually, I hope I got it right now (on the first try I
> crashed the whole database:( )
=========

Thanks Markku for cleaning out the old WU's ... :)
ID: 8145 · Report as offensive     Reply Quote
Profile Paul D. Buck

Send message
Joined: 2 Sep 04
Posts: 545
Credit: 148,912
RAC: 0
Message 8152 - Posted: 20 Jun 2005, 21:17:56 UTC

That is one feature I liked in Oracle, no autocommit. So, you could do a select to test the rows you thought you would affect, then run the update, then rerun the select to make sure only the right number of rows were affected. then do a separate commit to save the updates ...
ID: 8152 · Report as offensive     Reply Quote
Profile sysfried

Send message
Joined: 27 Sep 04
Posts: 282
Credit: 1,415,417
RAC: 0
Message 8154 - Posted: 20 Jun 2005, 21:36:45 UTC - in response to Message 8152.  

> That is one feature I liked in Oracle, no autocommit. So, you could do a
> select to test the rows you thought you would affect, then run the update,
> then rerun the select to make sure only the right number of rows were
> affected. then do a separate commit to save the updates ...
>
yup... nice... :-) but it can also have downsides.... imagine doing that via ssh oracle console... just before you commit, your connection drops...!!! *panic* ;-)
ID: 8154 · Report as offensive     Reply Quote
Profile Paul D. Buck

Send message
Joined: 2 Sep 04
Posts: 545
Credit: 148,912
RAC: 0
Message 8158 - Posted: 21 Jun 2005, 13:01:42 UTC - in response to Message 8154.  

> yup... nice... :-) but it can also have downsides.... imagine doing that via
> ssh oracle console... just before you commit, your connection drops...!!!
> *panic* ;-)

Then the session times out and the transations pending roll back to the state they were in prior to the change. No commit, no change ....
ID: 8158 · Report as offensive     Reply Quote
Kenneth Larsen

Send message
Joined: 2 Sep 04
Posts: 36
Credit: 90,806
RAC: 0
Message 8164 - Posted: 23 Jun 2005, 11:40:04 UTC - in response to Message 8141.  

> I invalidated these manually, I hope I got it right now (on the first try I
> crashed the whole database:( )
>
>

Thanks! :-)
ID: 8164 · Report as offensive     Reply Quote
Profile Markku Degerholm

Send message
Joined: 3 Sep 04
Posts: 212
Credit: 4,545
RAC: 0
Message 8166 - Posted: 23 Jun 2005, 12:24:04 UTC - in response to Message 8143.  

> be careful with your SQL "update" commands! ;-)

I was, but not careful enough... This one was actually in C code, like:

snprintf(buf, sizeof(buf),
"UPDATE result"
" SET (stuff) ",
" WHERE id=%d", stuff);

See where it goes wrong? :) The one extra comma between SET and WHERE which wasn't even this clearly visible due to overlong row... Well, from this lesson I learned to always printf() the SQL queries before executing them on the production database...


Markku Degerholm
LHC@home admin
ID: 8166 · Report as offensive     Reply Quote

Message boards : Number crunching : Old work still stuck in


©2024 CERN