| Time |
Nick |
Message |
| 08:35 |
|
mmorgan joined #evergreen |
| 09:12 |
|
Dyrcona joined #evergreen |
| 10:53 |
|
Christineb joined #evergreen |
| 11:01 |
|
sandbergja joined #evergreen |
| 15:33 |
|
adam_reid joined #evergreen |
| 15:35 |
|
adam_reid joined #evergreen |
| 15:57 |
* Dyrcona |
decides to implement a plpgsql function to "undelete" an item because there's nothing better to do at 4:00 PM on a Friday before a long weekend. |
| 16:04 |
Dyrcona |
Hrm.... |
| 16:36 |
jonadab |
Heheh. |
| 16:36 |
jonadab |
I mean, there's always changing the number of arguments an important function takes. |
| 16:39 |
Dyrcona |
:) |
| 16:39 |
Dyrcona |
Well, the function works. I made two versions: 1 takes the id number, and the other takes the barcode to get the id and call the first one. I'll likely use the second one more frequently. |
| 16:41 |
Dyrcona |
The second one decides which deleted copy to undelete (in case there's more than one) by getting the most-recently created copy. It also makes sure there are no not deleted copies with the same barcode. |
| 16:42 |
Dyrcona |
If the id variant hits a unique violation on the barcode during the update, then it returns. This way I can use it in transaction. My first use case is a list of 50 barcodes. |
| 16:43 |
Dyrcona |
I don't get asked to do this very often, but it has happened often enough that I decided to write a function. It also undeletes the call number and biblio record entry if necessary. |
| 16:43 |
mmorgan |
Dyrcona++ |
| 16:44 |
mmorgan |
I was just going to ask about the call number and bib! |
| 17:01 |
|
mmorgan left #evergreen |
| 17:34 |
|
adam_reid joined #evergreen |
| 18:38 |
|
adam_reid joined #evergreen |
| 18:54 |
|
adam_reid joined #evergreen |
| 19:16 |
|
adam_reid joined #evergreen |
| 20:07 |
|
adam_reid joined #evergreen |
| 20:51 |
|
adam_reid joined #evergreen |
| 21:09 |
|
adam_reid joined #evergreen |
| 22:00 |
|
adam_reid joined #evergreen |
| 22:51 |
|
adam_reid joined #evergreen |
| 23:33 |
|
adam_reid joined #evergreen |
