RE: [sqlite] Strange UPPER() behaviour

2005-01-18 Thread Drew, Stephen
OK, well I guess I should be moving to version 3 soon anyway! Another reason to give to my boss... Thanks for the help. -Original Message- From: Simon Middleton [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 1:11 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Strange

Re: [sqlite] Strange UPPER() behaviour

2005-01-18 Thread Simon Middleton
Drew, Stephen wrote: Simon, Thanks for the response. Two points: 1) The code is in the SQLite library, not my application. Oh yes - so it is. And in the copy I have here (v3) it does in fact use "unsigned char *". 2) Surely if chars are signed by default in MSVC, then islower() should work with

RE: [sqlite] Strange UPPER() behaviour

2005-01-18 Thread Drew, Stephen
- From: Simon Middleton [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 12:57 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Strange UPPER() behaviour Drew, Stephen wrote: > Hello, > I was running my application which uses SQLite in debug mode, and I > noticed some ver

Re: [sqlite] Strange UPPER() behaviour

2005-01-18 Thread Simon Middleton
Drew, Stephen wrote: Hello, I was running my application which uses SQLite in debug mode, and I noticed some very bizarre behaviour in this function: The character in question was the pound sign ('£') whose value the debugger said was -93 (the watch window however said 163). It seems that ins