Case sensitive column name problem

I have a strange problem in my application.
I install the application on several machines with no problem but in one machine I'm getting an exceptions on:
"Column 'SomeColumnName' does not belong to table"
the code look like this:
DataRow newDataRow = myTableFromDatabase.NewRow();
newDataRow["SomeColumnName"] = dr["SomeColumnName"];
when I change the code to upper case:
DataRow newDataRow = myTableFromDatabase.NewRow();
newDataRow["SOMECOLUMNNAME"] = dr["SOMECOLUMNNAME"];
it works on the problematic machine.
- I got the same problem on reading data from OracleDataReader.
- The property DataTable.CaseSensitive was not changed (default = false).
I'm not sure this is ODP problem or .net but I can't find any .net issues on that.

Ok ,
This is the most bizar bug that I ever saw:
The problem was that the machine was running in turkey.
In .NET culture settings the function ToUpper is not work on the letter 'i' when the region is turkey.
That means that oracle ODP OracleDataReader is case sensitive on the column name - if the column name have the letter 'i'.

Similar Messages

Problem in XI - JDBC (oracle) Scenario, case sensitive column name

I had a XI -> JDBC scenario, connecting to a SQL server, where the query was being generated using Message Mapping (XML SQL Format),
now the database has been migrated from SQL server to Oracle, and we are using the same XI scenario, but now the problem is, the query generated using message mapping doesnt work because it seems the query (UPDATE statement) requires the field name as having All capital letters, i mean the Column name in query to Oracle has become case sensitive,
can u help me out

Hi
Oracle doesnt have restriction that Query has to be in uppercase for any column. But it is good go use Upper case for the Query.
Use oracle editor to do the query if it is working fine and then use XML SQL in XI
Check this thread SAP has given some
http://help.sap.com/saphelp_nw04s/helpdata/en/43/68a541a1166153e10000000a1553f6/frameset.htm
Check FAQ on the JDBC adapter, see SAP Note 831162
always useful Note
Thanks
Gaurav

Case sensitive Tag names

Hi friends
I have a question, is it possible to transfer case sensitive tag names into xml structure ? for exemple, I want to transfer Tag name "DateCreated" . I did a test but start tag names is "DataCreated" and it is Translated in "DATACREATED" and this is a problem.
Thanks
Sergio

Sergio,
Usually what ever you have given in your xsd or message type you will have the same. So please check it. I just tested this and it seems to be the same as defined in your xsd or message type.
Regards,
---Satish

Case sensitive table names and column names in 8i or 9i databases

Hi everybody,
I've got a couple of business-side colleagues who insist that Oracle table and column names are case sensitive. That is, there is a setting in the set up of a database that lets you pick if table and column names are case sensitive. For example, this would mean that there could be a table named EMP in a given schema schema plus a table named emp in that same schema.
Can this be true? I'd be surprised of course, but I've been surprised before.
Thanks for any direction.
-- Bill Loggins

You can do it, but I would avoid it like the plague.
SQL> create table "a" (b date);
Table created.
SQL> create table "A" (b date);
Table created.
I think I would refuse to work on a database where this has been used !

Column name problem

Hi all.... I have a little strange problem.. I hope you all can help me in solving this.
for brief intro, I have an web application on MySQL written entirely in JAVA. Now we want to migrate from MySQL to Oracle... We have used Oracle Migration Workbench for migrating Schema and data. There is no problem uptill now.
The real problem is with the column names... to clear the problem lets have an example...
In mysql, if you execute[b] 'Select employeeID,empName from employee' you will always get 'employeeID' and 'empName' column names in the resultset meta data... but if you executes the same query on oracle you will get 'EMPLOYEEID' and 'EMPNAME' column names in resultset meta data... then we make some xmls using these column names and then parse them and get values using HashMap... now in hashmap 'a' is different from 'A'... We did not take care of this problem while building this application. Now the application is almost completed and we are just one step away from migrating to Oracle but this problem is hindering us.
just keep in mind there are several jsps,java beans, java services working on DB. So we need such a solution to apply on oracle and get our desired column names back from result set meta data.
I have tried multiple solutions for this.
1. Synonyms.. but you can only create synonyms for table not for column names
2. Create table with double qoutes... but then we have to change all our queries which requires a lot of files to change.
3. Create Views.... but it has same problem as of point 2.
Can you suggest any better way to work around this problem... which require minimum effort and we migrate to oracle with existing code... Otherwise we have to do a lot of donkey work to change the code...
Thanks in advance
Message was edited by:
user587592

migrate to oracle with existing code... Otherwise we
have to do a lot of donkey work to change the code...Is that not why SED/AWK/GREP and PERL were invented?
As others have said, the SQL standard as well as several implementations do not support mixed- or camel-case identifiers. IN addition, only 8 character identifers are required, all else is 'above the standard'. You are facing a typical porting issue.

Rowset column name problem

All,
I am a new user of JSC and am hopefully running into a simple issue. I've searched the forums here but so far have not found any postings regarding my problem. Apologies if this has been asked and answered before.
I am building a webapp to display data from a MySQL database. There are several places in the schema where I need to join to the same table multiple times. I have setup the joins in the query builder and also setup a view in the database directly that does the joins. Either way, the query works fine and returns the expected data. The trouble is that the rowset underlying the dataprovider is not returning the metadata using either the table&column aliases from the query builder or the column names from the view, but rather in all cases returning the underlying table and column names. In my table component I am trying to display the data from each table.column alias distinctly but because the metadata visible to the dataprovider is the same (ie table.column), I end up with both table columns showing the same data. I've tried to track down the implementation of the metadata getter method but it is apparently in source that is not provided.
In case it matters, I'm using mysql-connector-java-5.0.3-bin.jar as the driver.
Is there something I'm missing or is there a workaround for this?
Thanks in advance,
Scott

Thanks,
I should have been more explicit in my description of the problem.
Example of what I have is as follows:
select table1.columnA, table2.columnA as columnX,....
from table_name as table1 join table_name as table2....
where there are other tables and columns in the select clause as well as the join conditions but where the base table and column (in the above table_name.columnA) are used twice with two different aliases. I have done this join directly in the query builder and also created a view, hiding the actual names of the columns. I can execute either query in the query builder and the columns in the result set "spreadsheet" are labeled with the base table column names, not the aliased names or the view's column names. This is causing a problem because the same thing happens when I try to bind the ui:table columns to the dataprovider. It uses the base tables' column names and I have no way to distinguish between the different aliases. If I try to manually change the jsp to refer to the aliased name or the view column name, I get an exception that the aliased tablename and or column is an invalid parameter.
Sorry if that was not clear in my original post.

Loadjava column name problem

When trying to load compiled java classes, I always get the following:
Error while retrieving errors for BradTest
ORA-00904: invalid column name
resolver :
Error while resolving class BradTest
ORA-00904: invalid column name
loadjava: 2 errors
I get this error no matter what, even if I have an empty class with no methods or variables. I am using the following syntax for the loadjava:
loadjava -user id/password@host:1521:SID -t -r -v BradTest.class
Any ideas what the problem is?
Thanks,
Brad

Sounds as though the JVM may not be correctly or completely installed. You may need to rerun the INITJVM.SQL script (as sys) and check the alert log for errors.

Invalid Column Name Problem

Hi..
I have a table component and that is bound to a Database Table.
I have button name "UPDATE" which commits changes to DB.
When I press "UPDATE" button an error occurs...
Number of conflicts while synchronizing: 1 SyncResolver.UPDATE_ROW_CONFLICT row 0 [sunm][SQLServer JDBC Driver][SQLServer]Invalid column name 'date'.I dont have any column name "date".
I tried my best but not yet successful..
Thanks
Tariq

Hi RK,
Here is the SQL Statement
SELECT ALL dbo.DailyFlyingProg.FormationNo,
                    dbo.DailyFlyingProg.TailNo,
                    dbo.DailyFlyingProg.Pakno_Front,
                    dbo.DailyFlyingProg.Pakno_Rear,
                    dbo.DailyFlyingProg.MissionID,
                    dbo.DailyFlyingProg.Config,
                    dbo.DailyFlyingProg.Ready,
                    dbo.DailyFlyingProg.Take_Off,
                    dbo.DailyFlyingProg.Ess_Exe,
                    dbo.DailyFlyingProg.Area,
                    dbo.DailyFlyingProg.Stack_EAC
FROM dbo.DailyFlyingProg
WHERE dbo.DailyFlyingProg.Date1 = ? Thanks
Tariq

Datagrid column name problem

Hi;
I'm new to flash AS.
Datagrid column name codes..
Code:
var dp:DataProvider = new DataProvider();
dp.addItem({column1:"xx", column2:"xx", column3:"xx" });
works fine but if i'm change column name to numeric value (eg:32) gives me error..
Datagrid is not supported numerical value?
Thanks for help..

Worked fine..
Thx for your help!

UTL_FILE & User Input: Case Sensitive File Names

Hi.
I'm trying to reduce problems due to the whether the user uses upper or lower case or combo of them in entering file names.
Scenario is:
Existing file to be read: Orig_File.Txt (file name changes daily)
Output to be saved into file: RESULTS_FILE.TXT
In response to PL/SQL commands (please see below), the user enters:
ORIG_FILE.TXT and Results_FILE.txt
as the Input & Output file names. The problem is that the input file has been saved using Upper and Lower case and I get back a file not found error.
Is there a way to call a file with is a different case than the input?
Thanks.
Current commands are:
In_File          UTL__File.file_type;
Out_File          UTL__File.file_type;
Curr_Line     VarChar2(2000);
BEGIN
In_File := UTL__File.fopen('UTIL_FILE_DIR', '&input_file', 'R', 2048);
Out_File := UTL__File.fopen('UTIL_FILE_DIR', '&output_file', 'W', 2048);
LOOP
BEGIN
UTL__File.get_line(In_File, Curr_Line, 2048);
.......

A shell script would typically issue something along the lines of
newfile=$(ls -C1 | grep -i "\<${filename}\>")although of course it is possible for this to match multiple filenames, so it would have to check for that scenario and report it as an error. possibly you could call a shell script like this from PL/SQL via Java or DBMS_SCHEDULER. Good luck with that though.

Case Sensitive File Names

Hi...
I've been trying out the trial version of RH8, before
upgrading from RH7. One of the problems I have noticed is the
option to "Use Lowercase File Names (Recommended for UNIX)" in the
Single Source Layouts setting, only works for actual pages in the
project. As i have a number of PDF's as baggage files (that now get
indexed), when they are returned in the search results, I just get
a "Not Found" error. This is because it is not correctly putting
the folder names or file names in lower case.
Does anyone know a solution or workaround for this? (aside
from renaming all files/folders!). Or know where I can submit this
as a bug?
Thanks...

Bug/Feature requests can be filed
here..
As a workaround, you could try renaming your baggage files - for
example File.pdf to file1.pdf and then to file.pdf. You'd need ot
delete and add the baggage file references though. An alternative
is to exclude the baggage file type from the search. You can find
out how to do this from the latest post on my blog.

Retaining case sensitive path names

We are currently using initial capital letters for our directories in our path names. But every time I update my Fireworks file it automatically changes all directory names back to lower case, thus breaking our links on our web pages. Is there a way I can configure Fireworks to retain my Upper Case first letters of my directory names after I've updated the Fireworks file?

Hi Jim,
Thanks so much for your help--much appreciated!!

BUG: Export DDL and Data fails for mixed case table/column names

Hi there,
I have found a bug in SQL Developer. See details below.
Description:
When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
- you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
- add some data rows to the table
- choose Tools -> Export DDL and Data
- check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
-- DDL for Table lowerCase
CREATE TABLE "DBO_HT"."lowerCase"
(     "lowerCol1" VARCHAR2(100),
     "UpCol2" VARCHAR2(100),
     "ALLUPCOL3" VARCHAR2(100)
-- DATA FOR TABLE lowerCase
-- FILTER = none used
-- INSERTING into lowerCase
Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
-- END DATA FOR TABLE lowerCase
Remarks
SQL Developer: version 1.2.1, build MAIN-32.13
Oracle DBs: 9.2 & Express
OS: Windows 2000 Professional
If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
Thanks a lot & bye

Thanks for your reply.
ad. 1)
You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
ad. 2)
Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
That's, IMHO, the way to attract more Express users.

Case sensitive table names

Hi all, I create a table named "Organism" on my marvel schema. When I do a SELECT * FROM "Organism", I get correct results, but when I try to do
DESC "Organism"
I get an error message saying the table doesn't exist.
Is there something I am missing ?
regards,
Davide

hmmm. it looks like you found a tiny bug in our Ad Hoc module within the SQL Workshop. you can get around it for now by browsing for your table in the Data Browser of the SQL Workshop. it just appears that in the SQL Workshop we haven't accounted for the cases where people are defining their objects with mixed case text. it's a super easy fix on our part, though, so i imagine we'll see things working more smoothly soon.
regards,
raj

Problem with column names

I have named my columns for exaomple column trasanctionid as "TransactionID".But when i write a process and run the query in the process it takes the column name as all in cappital letters.Hence it gives me follwing error.
ORA-00904: "TRANSACTIONID": invalid identifier
I want to know whether there is any constraint to name columns all inc apital letters in apex.I am finding it difficult to change column name and then make changes throughout the app for it.This error has popped up many times for me and I had to everytime change the column anme to all capitals to get rid of this error.
Edited by: dwitiya on Sep 3, 2010 10:52 AM

Glad to hear it.
And as you can see from the other responses, case sensitive column names are not widely understood (many people assume they don't exist), so it's really best to avoid them wherever possible. The only time I've seen column names defaulting to case sensitive was when we imported a table from Microsoft Excel using a third-party tool (Toad). This caused us a rather significant amount of headache, and it's something I've been careful to check for ever since.
Of course, once a table or a column is created with a case-sensitive name, it can be hard to break free, as you're discovering--you can't just alter the table and rename the column, as your existing code will break. (transactionid is equal to "TRANSACTIONID", but not "TransactionID".) So if you're not willing to go through your entire codebase to fix the case-sensitivity (and most of us don't have time to), you're going to have to get used to putting quotes on the things that need it.
Which will, of course, help you remember to make your table and column names case-insensitive in the future. :-)
-David
Edited by: DavidG on Sep 3, 2010 11:17 AM: realized I'd mis-typed a variable name.

Case sensitive column name problem

Similar Messages

Maybe you are looking for