| Time |
Nick |
Message |
| 03:06 |
|
jeff joined #evergreen |
| 08:46 |
|
mmorgan joined #evergreen |
| 09:04 |
|
Dyrcona joined #evergreen |
| 10:04 |
|
mmorgan1 joined #evergreen |
| 10:13 |
csharp_ |
@decide opensrf or opensrfg |
| 10:13 |
pinesol |
csharp_: go with opensrfg |
| 10:17 |
Dyrcona |
heh. I made an interesting typo myself just now: action_tigger.event_definition... I usually typo the definition part, not the action_trigger part. |
| 10:18 |
Dyrcona |
Maybe I should alias tigger to the action_trigger schema. It seems appropriate. |
| 10:23 |
Dyrcona |
Guess you can't alias a schema. |
| 10:28 |
|
Guest26 joined #evergreen |
| 11:14 |
|
Rogan joined #evergreen |
| 11:37 |
|
jihpringle joined #evergreen |
| 13:29 |
* Dyrcona |
tries to figure out a rough date when we added Quipu. |
| 13:31 |
Dyrcona |
Having squashed and rebased doesn't help with the archeology. |
| 13:34 |
Dyrcona |
looks like when we upgraded to 3.5.3...We've had that for a while. |
| 13:49 |
* Dyrcona |
is going to insert the upgrade numbers into config.upgrade_log so it doesn't look like we missed those. |
| 13:55 |
Dyrcona |
I guess I should test my latest custom db upgrade script again. |
| 14:01 |
Dyrcona |
Looks like it will still work after that insertion. |
| 14:05 |
Dyrcona |
The upgrade values would be inserted by the custom upgrade if they're not there anyway, but I'd like to have the actual dates that we started using the code in the upgrade log. |
| 14:05 |
Dyrcona |
@quack |
| 14:05 |
pinesol |
Dyrcona: CHOWN ARE OPENSRF COLON OPENSRF OPEN EYE ELL ESS |
| 15:44 |
|
jihpringle joined #evergreen |
| 16:09 |
|
jihpringle joined #evergreen |
| 16:59 |
|
mmorgan left #evergreen |
