Case sensitive usernames for wiki

Hi I'm running the wiki services which get the usernames and passwords from another server which have upper and lowercase usernames, is there a way to ignorecase on usernames for the wiki? so if i type
MSmith or msmith it still lets them login?

Hi,
AFAIK usernames whether Full or short names are case sensitive in OD. The wiki uses Password Server to authenticate against a user account. UserManagementv10.5.mnl for 10.5 Server describes the Open Directory creation and modification of a user account and the rules for Full and Short names. Case insensitivity is not covered.
Using an add on script such as LDAP authenticators communicating with OD can implement any policy you want. But out of the box OD is case sensitive.
HTH,
Harry

Similar Messages

Case-sensitive search for equipments

Hello gurus,
when looking for certain equipments using F4 (program RIEQUI20), I can search for all equipments of a certain manufacturer (field HERST).
Unfortunatelly this search is always case-sensitive, i.e when I enter "BOSCH", equipments with manufacturer "Bosch" are not found and vice versa.
Is there any way to change this behaviour?
Thanks in advance
Alicia

Alicia,
Oops ..Sorry about that. I had misread it. You will not be able to accomplish the same in standard enhancement.You could remove the case sensitive check box on the HERST data element.But that would be considered A modification.That might however do the trick and save all the new contents in CAPS.The search help will then pick everything.(You may have to go into change mode on existing records and re save them for this change to be updated in DB )
However you could achieve the same, without modification and with a little bit of custom development.
What you could do is, create a Custom elementary search help(SE11) with the standard fields HERST(Input) and EQUNR(Output) fields .Create and Attach a custom Search help exit to the same by copying F4IF_SHLP_EXIT_EXAMPLE. In here modify the STEP SELECT to append a translated (Upper and lower case) selection condition to the query or a appropriate wild card search.Then select the same from EQUI.This should pull all your records. After testing this out , append this search help to the standard collective search help EQUI.
Hope this helps.
Regards
Narasimhan
Edited by: Narasimhan Venugopal on Jan 7, 2010 10:24 AM

Case sensitive Usernames and deleting users

I created a user in a new database and did not get the case correct. It needed to match a username in another database, since it was, in fact, the same user and I did not want to unnecessarily burn another license. Since this newly created user had not made any transactions, I simply deleted the user so that I could create it in the proper case. No Go. The user no longer appears in SAP as a user, but it still exists in the OUSR table. As a result, I am unable to create it with the correct case.
Please let me know what the best course of action is to correct this error.
Randy Davis
Denver

Hi,
You can check the Note No. : 869326 regarding the issue reported by you.
Hope it helps.
Kind Regards,
Jitin
SAP Business One Forum Team

How to solve this case sensitive problem for the parameters in function?

Hi,
   I have a function, which should receive one parameter comes from textbox in BSP form. User will input upper case or lower case characters together in this textbox. But when I debug function, I found after function recevice the value from BSP form, the string value was converted into upper case automatically.
   I don't want system convert string to upper or lower case. I want keep the original value that user inputted.
   So is it possible to do this?
   Thanks!

Hi,
   Thanks for your reply.
   Yes, I use the inputfield. The problem is if I use the parameter which contain user's input in the event handler of BSP, the value is equal to the user's input. But if the parameter was transfered into function, the value was converted to uppercase.
   But I want to keep the original value.
   Thanks!

Case Sensitive External Drive for iTunes

My iTunes Library is currently stored on a case sensitive external drive. I am moving it to another drive that I found out is formatted as a non-case sensitive (both areJournaled). When I tried to move my iTunes Library, it would not copy because there are apparently some duplications that are different in case and this causes a problem when duplication to a non-case sensitive drive.
I figure I have two options:
1) Reformat the new drive to be Journaled and Case Sensitive
2) Go through the tedious process of identifying which files in the iTunes Library would be duplicates in a non-case sensitive drive. There could be just a few or hundreds (or even thousands).
What is the disadvantage of using a Case Sensitive drive for iTunes (option #1)? I may also store some other files on this drive.
I noticed that all my other drives, on both my desktops and external are formatted as non-case sensitive.

If you can get to the two metadata files that iTunes keeps on the old PC, then you have several options. See: What are the iTunes Library files?
1) Use the 'iTunes Library.itl' file on the old PC to completely recreate your Library. You will have to place all the music files/folders in the exact same location on the new PC as they were on the old PC. That drive letter and directory path. Then copy the older ITL file over the current one on the new PC. Open iTunes and you'll have a clone of the old PC's Library. As you have been using an ExHD to store the music, this would be my preferred choice. It's easy to remap the drive letter of an ExHD, if needed.
2) The other way is to 'File=>Import' the XML file and recover the Playlists from there. They will not be in any folder structure as they were in the previous iTunes. Also, any playlists that depended on ratings, play counts and last played will be changed, as those attributes have not been carried over using this method.
Post back if you have questions.

Turn off case sensitive for whole system

Hello,
I am looking for the feasibility to turn off the case sensitive functionality for the whole system. Is it ever possible?
Thank you in advance.
Dmitri

Dmitri, at this time it is not possible to turn off the case sensitive functionality. I would recommend that you submit a enhancement request to CRM On Demand customer care.

Is a Full Text Index search case sensitive or not in SQL Server 2012?

I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
Hanan

Whats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

When logging onto a web site with a log on name firefox is changing logon name from Kostas to kostas as the site is case sensitive it is not acceptable. how do I correct this? Thanks

I registered with a web site and used the name Kostas as the log on name. Entered a question and recieved replies
When I later tried to log onto the web site to say thankyou ,and enter Kostas in the log on box a reminder appears created by Firefox of kostas, I ignore this, move to the password box and firefox changes the log on name to kostas with small k. The register is case sensitive so for quite a while I could not understand what was going wrong? I eventually managed to log on by using a rival system
My previous experience is that if you use a different log on name it is recorded and then you choose the correct one to use? But in this case I am given no choice
How can I correct this please
Probably no connection but
I registerd with another site and recieved an e-mail in which I had to click on web address to confirm registration and came up with an error message, tried a few times and same thing happened?? The webmaster of this site had no record of my registration details?
Finally I had a phone call from a company called NERD-I.com
offering to solve various computor problems at a fee. I did not take up their offer, but hope they do not have anything to do with my current problems??
Many thanks

Hi Corel
Thank you for your reply
However I need the lower case version for some sites and the upper case version for the site in question? To make matters worse this site does not allow you to change your log on name unless it is in the form of an e-mail address
So what I need is Kostas for this site and kostas saved for other sites and allow me to choose which one I want to use
How do I do this please
I have no bother with this on Win Internet Explorer but I like Firefox
Mind it may be as simple as deleting The appropriate entry and resetting with Kostas instead of kostas?
But I would appreciate knowing the correct solution from an expert

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 !

File System Case Sensitive - breaks Write-Once

I don't find a System property that denotes if the file system is case sensitive.
If I want a FileFilter to behave as the user is expecting - it must know if the file system that it is running on is case sensitive. For example: On a DOS system the file apple.txt should be returned with the file PEACH.TXT by a FileFilter that is accepting *.TXT files. But on a Unix system only the PEACH.TXT would be returned (case sensitive).
How would I make my FileFilter a true write-once-run-anywhere class?
What am I missing?
David

For a file filter,
you can get the file name and convert it to lowercase,
then compare to a lowercase extension. It's not like
that will rename the file, the file will still have
whatever name the file has. However for a FileFilter that is case sensitive - there is a difference in what a File.listFiles(new ExtensionFilter("txt")) returns. And one can not just decide that it doesn't matter.
Here's a specfic example. On a case insensitive system what is the next file in the sequence of:
File.001, File.002, File.003, file.004
Answer: fILE.005 - is valid
But on a case sensitive system if one uses a FileFilter to find all the files that match "File".* then the answer is "File.004" - ONLY ONE answer, and creating this file will not (should not) overwrite the file.004!
Seems to me one needs to match the FileFilter to the underling OS - because chances are the user is expecting OS file system naming conventions. If the user doesn't know what file system (and can't know - like on a web server app) then the system better be smart enough to not mess up and clober files.
So it appears to me that a programmer needs to be able to ask the System what it's file system convention is. And sure I could guess based on some other properties (System.os.name or as Sun did based on file.separator) - but I was hopeful that I didn't need to GUESS.

Copying Files from Case-Sensitive External to Non-Case-Sensitive Internal?

+(Sorry if this is the wrong sub-forum, I didn't know which one this question fit in)+
I just got a new iMac today and I'm trying to transfer some of my old files (specifically iTunes & iPhoto). My old computer was an MBP & only had an 80 GB HD, so these files were run off an external drive.
I know basically how to copy these files onto my new computer. The problem is that my external drive is formatted as Mac OS Extended (Case-Sensitive, Journaled). So when I try to copy the iTunes or iPhoto folder, I get the following message:
+You can’t copy “iTunes” because it has the same name as another item on the destination volume, and that volume doesn’t distinguish between upper- and lowercase letters in filenames.+
The only option I know of is to reformat my iMac's drive as Mac OS Extended (Case-Sensitive, Journaled). Since Macs ship with the drive formatted as Mac OS Extended (Journaled), I assume that's the best option, and would prefer not to reformat if I don't have to. I've also read that some programs won't run on a case-sensitive drive.
*Do I have any easy alternatives to move my iTunes/iPhoto folders?*
*If not, what negatives do I need to consider when reformatting my iMac's drive to a case-sensitive one?*
Thanks.

Joel-X wrote:
I've solved the problem for iTunes, but it was a bit tedious.
Yes, I'll bet! It would be sooo much easier if the Finder would produce a list somewhere.
*Assuming that I solve the "case-sensitivity problem" for my old "iPhoto Library" folder, will a simple drag and drop of that folder to my new iMac allow me to just open iPhoto 9 and have all my photos be there?*
I believe so, as that's how Apple tells you to move it: [Moving your iPhoto library|http://support.apple.com/kb/HT1229].
I don't want to spend too much time on the case-sensitivity problem until that question is answered, just in case.
It may not be as easy to solve, though. That library is a "package," kind of like an app -- actually a folder, but treated as a single object for most purposes. If you right-click it via the Finder and select +Show Package Contents,+ you'll see the file/folder structure.
See the note in the link above -- it sounds like changing file names will break the structure; it may only affect the files you change, but it might be worse.
If you can find the duplicates, you may be better off exporting them via iPhoto, deleting them via iPhoto, then re-importing them under different names. That should keep the structure intact.
At the very least, make a full copy somewhere before touching it.
Good luck!

Query Variable: F4 search by Text is case sensitive in Web Templates.

Hello Guru's,
I have a problem, when I am trying to search the variables in Web Templates the search by text is case sensitive.
For example If I have the customer name as "King", I have to search the text as King or Ki*, But If I search as king I will not get any results.
I need to have my text search as case insensitive.
When I checked in my BEx queries the search is case insensitive. I have the problem in my Web Templates only. Please let me know do I need to change any variable settings ing the web templates or let me know how do I fix this issue.
Many Thanks,
Vamshi Krishna

Hi,
So the only workaround for this would be to goto RSD1 -> enter info
-object as xxxx, and press maintain, then goto master data/text
tab and select the check box, 'with text', now save and activate the
infoobject. After this regenerate the query using tcode rsrt.
To regenerate goto rsrt enter query name and press 'generate report'
button.
Now the F4 help screen should show the options search by key and search
by text. So that you can select serach by key to have a case insensitive
search.
Thanks,
Venkat

Renaming filenames and case-sensitivity: a race condition in the OS?

There appears to be a curious set of circumstances where the OS doesn't allow you to rename a file where the only changes are case-sensitive. For example, "foo.JPG" to "foo.jpg". You can see an example using the command-shell "tcsh". Start this shell (type "tcsh" at any command prompt), and then type:
% touch foo.JPG
% mv foo.JPG foo.jpg
overwrite foo.jpg? (y/n [n])
Now, you may think it's no problem because few people use tcsh, but the problem is more systemic that should be addressed because I'm finding the problem at a programming level as well. The simplistic tcsh example illustrates the problem: the internals of tcsh call the OS-layer library function rename(2) to move or rename a file. However, something in the OS that reports back that the new filename exists (even though it doesn't) Because it sees foo.JPG, and it doesn't differentiate letter case, it thinks foo.jpg exists, so it returns an error to the calling program. In this case, it's tcsh, which is what prompts the user to overwrite. It doesn't matter what you answer, the result is the same. If you say yesthe OS doesn't see them as different, so it doesn't do anything.
If you're a programmer, you can see this happen for yourself by writing a small program that does the same thing:
#!/usr/bin/perl
if (!rename "foo.JPG", "foo.jpg") {
print "Error: $!\n";
This simple perl script just calls the rename(2) library call, which is part of the OS.
What I don't understand is why this error happens, when, and how to get around it. Obviously, other programs that rename files don't have this problem. The default shell, bash, doesn't have a problem either--even though tcsh (also a similar command-line shell) does. In fact, most programs don't have this problem. But as a programmer, I'm not sure what I should be doing. This exact same perl script (and correlating C programs) work perfectly well on all other unix platforms I've tried.
G5 Mac OS X (10.4.5)

It's not at the os layer, it's at the filesystem
layer. The filesystem you have is not case sensitive.
well, the filesystem is part of the operating system, although it's clearly only one component of it. In fact, one of the primary defining characteristics of unix is how the filesystem works, albeit there are variations of implementation. But this is a nit=picking point.
As to the issue of whether the filesystem truly is case-insensitive, that isn't so clear. I can rename a file from foo.JPG to foo.jpg easily in the Finder (just click and edit a file to change it's name from upper to lower, or mixed), and the new name you give it DOES change. similarly, I can do this with virtually any other app that has a file-finder style dialog box. Why I can't do it with the shell (or at an API level) is the real mystery, and there is no doc on the subject that I'm aware of. Clearly, the OS is preserving the change somewhere, somehow. the question is, who's doing it? (and if it's not part of the filesystem, why?)
It could be that some other layer is sitting on top of the filesystem that is overseeing such actions, and is preserving the case of the filenames, but this is such a huge waste of time and work, all for a "feature" whose value is still as yet unclear to me.
If it is, as you say, that "my version" of the filesystem happens to be case-insensitive, I'd love to know where that came from, and what the rationale was behind it. And, of course, how to get some version of the filesystem that doesn't have this feature. I've been working with unix systems at every layer since 1983, and have never run into such a thing before.
dan

Paramenter Value Case Sensitive Setting

Is there a setting in the pref.txt file (or any place else) to change the actions of the case sensitive setting for entering parameter values? Turning it off/on. Changing the case sensitive setting in the condition that contains the parameter does not modify the parameter value entry window functionality.
Thanks,
Jerre

Hi Jerre
I'm afraid there is no preference that can be set to control the casing of the values keyed in a parameter. You would have to do this yourself by embedding the value of the parameter into a calculation and use UPPER or LOWER accordingly.
The option you are referring to controls whether Discoverer should literally take the value keyed in the parameter as the filter for the condition or not. It does not change the casing of the parameter for other uses.
Best wishes
Michael

Case sensitive usernames for wiki

Similar Messages

Maybe you are looking for