Hi all; after running our productive environment atop MaxDB quite successfully for one week now, I am pretty pleased with the performance of the system and happy we did this. Anyhow, by now there always are some small issues bugging me in where MaxDB behaves different to how MSSQL used to behave, leaving me with the need of finding workarounds or "real" new solutions.
My current problem is that MaxDB uses to respect or ignore upper/lower case letters in different situations than MSSQL. On one side, I see that our table names now are all upper-case, while they used to be mixed case on MSSQL. That's okay, because it works. What is not so fine is that, on the other side, in our productive system suddenly there is case sensitivity within the table content. For example, searching for documents using a pattern like "INV" within our document management system originally used to find ... INV_001 INV_002 Inventory_2004 ... paying no respect to upper/lower case letters. Now, running the system atop MaxDB, searching for INV only returns ... INV_001 INV_002 .. indeed paying respect to the fact that upper/lower case letters are different. The point is: By now I thought that SQL is case-insensitive, but obviously in this situation, it's not. Is this a specific behaviour of MaxDB, or should I make up my mind about case sensitivity in SQL? Is there, anyhow, a smart / clean way to get out of this situation without breaking too much glass? Hope for some short hints... TIA and have a nice weekend everyone, Kris -- Kristian Rink -- Programmierung/Systembetreuung planConnect GmbH * Strehlener Str. 12 - 14 * 01069 Dresden Tel. 0351 4657716 * Fax 0351 4657707 * [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
