Case sensitive or not
No edit summary
(Automatically adding template at the end of the page.)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==== Tagged values ====
==== Tagged values ====
When it comes to tagged values - the value is just a string and it is up the implementer how the interpretation is done -> case-to-case. Having said that we ''aim to have all boolean tagged-values to be case insensitive''. If you find exceptions to this ambition it would be great if you report it so that we can fix it.
When it comes to tagged values, the value is a string. It is up to the implementer how the interpretation is done -> case-to-case. Having said that, we ''aim to have all boolean-tagged values as case insensitive''. If you find exceptions to this ambition, it would be great if you reported it so that we can fix it.


==== OCL ====
==== OCL ====
Ocl is largely case-insensitive when it comes to identifiers and operators BUT types must start with a Capital-letter. Data in MDriven is always case sensitive; operators [[OCLOperators ToUpper () : String|toupper]], [[OCLOperators ToLower () : String|tolower]], [[OCLOperators sqlLike|sqllike]] and [[OCLOperators sqlLikeCaseInsensitive|sqllikecaseinsensitive]] handles case conversion.
OCL is largely case-insensitive when it comes to identifiers and operators BUT types must start with a Capital-letter. Data in MDriven is always case sensitive; operators [[OCLOperators ToUpper () : String|toupper]], [[OCLOperators ToLower () : String|tolower]], [[OCLOperators sqlLike|sqllike]] and [[OCLOperators sqlLikeCaseInsensitive|sqllikecaseinsensitive]] handle case conversion.


==== OCL-PS / Database ====
==== OCL-PS / Database ====
When creating SQL-Server instances you can decide what collaction to use - collations containing "_CI_" in the name are case insensitive, others are case sensitive. We offer OCL operators sqllike and sqllikecaseinsensitive.  
When creating SQL-Server instances, you can decide what collation to use. Collations containing <code>"_CI_"</code> in the name are case insensitive while others are case sensitive. We offer OCL operators [[OCLOperators sqlLike|sqllike]] and [[OCLOperators sqlLikeCaseInsensitive|sqllikecaseinsensitive]].  


In the persistencemapping set up for MDrivenServer we use bit to represent bool in the database -> 1==true, 0==false. If you have DefaultDbValue on a boolean you must put 1 or 0.
In the persistence mapping setup for MDrivenServer, we use a bit to represent bool in the database -> <code>1==true</code>, <code>0==false</code>. If you have DefaultDbValue on a boolean, you must put 1 or 0.
[[Category:Database]]
[[Category:Tagged Values]]
[[Category:OCL]]
{{Edited|July|12|2024}}

Latest revision as of 15:27, 10 February 2024

Tagged values

When it comes to tagged values, the value is a string. It is up to the implementer how the interpretation is done -> case-to-case. Having said that, we aim to have all boolean-tagged values as case insensitive. If you find exceptions to this ambition, it would be great if you reported it so that we can fix it.

OCL

OCL is largely case-insensitive when it comes to identifiers and operators BUT types must start with a Capital-letter. Data in MDriven is always case sensitive; operators toupper, tolower, sqllike and sqllikecaseinsensitive handle case conversion.

OCL-PS / Database

When creating SQL-Server instances, you can decide what collation to use. Collations containing "_CI_" in the name are case insensitive while others are case sensitive. We offer OCL operators sqllike and sqllikecaseinsensitive.

In the persistence mapping setup for MDrivenServer, we use a bit to represent bool in the database -> 1==true, 0==false. If you have DefaultDbValue on a boolean, you must put 1 or 0.

This page was edited 94 days ago on 02/10/2024. What links here