(no subject)
Oct. 16th, 2009 01:36 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
In addition to it being quite cold out today, it is now raining.
Hmmm.
I was supposed to go to the grocery store for a tin of coconut milk.
For a curry.
i'm not really wanting to get off the bus if it's raining.
However
I do have a carton of whipping cream that may suffice, with a bit of diluting with milk.
My arteries will thank me if i dilute. Must look in the cupboard and see if i have any coconut extract then i'd at least get the flavour.
Had lovely mac and cheese for lunch with a side salad. (Treats, Scotia Square in case anyone local is interested)
Geek warning....
Probably a good thing the Data Base Administrator is out of town. He would have been kissed soundly (on the cheek) today because he sorted something that in turn fixed a baffling problem i'd been having for a few days. I hate it when things go wrong for no apparent reason. Sometimes it's a piece of the puzzle that goes corrupt for some unknown reason. Sometimes it's a change i've made but in this case it was neither and the error messages were confusing and misleading considering what was actually going on. See, last week a password was about to expire so he changed it to an indefinite expiry date. This was important because it was a behind the scenes password that an application used and we couldn't have it just stop working one day because the password expired. But, when you log in now, the database throws up a message to say the password will expire in (20 digit number) days. But you can still log in. Only the application, when running on my local machine out of the programming developer software, kept telling me it couldn't connect to the database, saying the character set was invalid. There was no expiry message on the software console, only if i tried to connect using something more direct (sql-plus) No problems with the application that was running independently on a server, either, only when running it on a local machine server. But I hadn't changed anything. The DBA noticed the expiry message and got rid (from his remote location) and lo and behold, we have connection! I think what happened was that the local server/connection piece didn't know what to do with the message and couldn't recognize a 20 digit number in it's native format and horked up a hairball with the closest related message it could find. Gah!
Anyway, sorted now. I can relax and enjoy the weekend.
Hmmm.
I was supposed to go to the grocery store for a tin of coconut milk.
For a curry.
i'm not really wanting to get off the bus if it's raining.
However
I do have a carton of whipping cream that may suffice, with a bit of diluting with milk.
My arteries will thank me if i dilute. Must look in the cupboard and see if i have any coconut extract then i'd at least get the flavour.
Had lovely mac and cheese for lunch with a side salad. (Treats, Scotia Square in case anyone local is interested)
Geek warning....
Probably a good thing the Data Base Administrator is out of town. He would have been kissed soundly (on the cheek) today because he sorted something that in turn fixed a baffling problem i'd been having for a few days. I hate it when things go wrong for no apparent reason. Sometimes it's a piece of the puzzle that goes corrupt for some unknown reason. Sometimes it's a change i've made but in this case it was neither and the error messages were confusing and misleading considering what was actually going on. See, last week a password was about to expire so he changed it to an indefinite expiry date. This was important because it was a behind the scenes password that an application used and we couldn't have it just stop working one day because the password expired. But, when you log in now, the database throws up a message to say the password will expire in (20 digit number) days. But you can still log in. Only the application, when running on my local machine out of the programming developer software, kept telling me it couldn't connect to the database, saying the character set was invalid. There was no expiry message on the software console, only if i tried to connect using something more direct (sql-plus) No problems with the application that was running independently on a server, either, only when running it on a local machine server. But I hadn't changed anything. The DBA noticed the expiry message and got rid (from his remote location) and lo and behold, we have connection! I think what happened was that the local server/connection piece didn't know what to do with the message and couldn't recognize a 20 digit number in it's native format and horked up a hairball with the closest related message it could find. Gah!
Anyway, sorted now. I can relax and enjoy the weekend.
no subject
Date: 2009-10-17 01:23 am (UTC)no subject
Date: 2009-10-17 01:40 am (UTC)