Case-sensitivity

Tim S

I have a developer who is trying to automate the upload of documents.The code tries to find the existence of a file before it attempts to create a new document. When they run the query OpenText “thinks” that the file doesn’t exist but it does with a different letter casing (e.g. "Q3.2017pressrelease.pdf" vs "Q3.2017PressRelease.pdf"). Is this a known issue? Is there any way to specify the query to ensure that the file name is found regardless of the case of the name?

Appu Nair

Perhaps this old thread might give you some ideas or may ask in the search indexing forum

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=53391097&objAction=viewincontainer

if this has changed or not.

As a workaround can you developer resort to finding it using a DB query?

SELECT

Appu Nair
Principal Architect | Alitek
Website: alitek.com

---

From: eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com>
Sent: Friday, December 8, 2017 2:13 PM
To: eLink Recipient
Subject: Case-sensitivity

 

Case-sensitivity

Posted by tim.saunders@guggenheimpartners.com (Saunders, Tim) On 12/08/2017 12:52 PM

I have a developer who is trying to automate the upload of documents.The code tries to find the existence of a file before it attempts to create a new document. When they run the query OpenText “thinks” that the file doesn’t exist but it does with a different letter casing (e.g. "Q3.2017pressrelease.pdf" vs "Q3.2017PressRelease.pdf"). Is this a known issue? Is there any way to specify the query to ensure that the file name is found regardless of the case of the name?

---

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	My Support

 
Confidentiality Note: This message contains information, which may be privileged or confidential, or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee responsible for delivering the message to the intended recipient, you are hereby NOTIFIED that any dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you receive this message in error, please notify sender immediately.