On Unix, table names are case sensitive. On Windows, they are not. Fun, isn&#39;t it? Kinda like their respective file systems. Do you think it&#39;s a coincidence?

In other words, if you are developing on Windows but planning on deploying to a Linux machine, better test your SQL against a Linux-based MySQL too, or be prepared for mysterious &quot;table not found&quot; errors at prod time. VMs are cheap these days.

Field (column) names are case-insensitive regardless.

EDIT: we&#39;re talking about the operating system on the MySQL *server* machine, not client.

From the MySQL [documentation][1]: 

&gt; database and table names are not case sensitive in Windows, and case
&gt; sensitive in most varieties of Unix. One notable exception is Mac OS
&gt; X, which is Unix-based but uses a default file system type (HFS+) that
&gt; is not case sensitive.

and

&gt; Column and index names are not case sensitive on any platform, nor are column aliases.



  [1]: http://dev.mysql.com/doc/refman/5.6/en/identifier-case-sensitivity.html

For database and table names, it depends on the underlying operating system.
See [8.2.2. Identifier Case Sensitivity][1] 


  [1]: http://dev.mysql.com/doc/refman/4.1/en/identifier-case-sensitivity.html

Strangely enough it *seems* to be case sensitive in the MySQL Workbench even on Windows.

We just tried to alter the results of a SELECT statement but the Workbench didn&#39;t let us, complaining that our query did not include the table&#39;s primary key (which it did but in lower-case) so the result was read-only. Running the same query with the primary key in proper case (ID instead of id) would let us edit the results as expected.

Is JVM open source code? If not, how can I get the code of JVM?

Is JVM open source code?

I&#39;m trying to use a function with PostgreSQL to save some data. Here is the create script:

    -- Function: &quot;saveUser&quot;(integer, character varying, character varying, character varying, character varying, character varying)

    -- DROP FUNCTION &quot;saveUser&quot;(integer, character varying, character varying, character varying, character varying, character varying);

    CREATE OR REPLACE FUNCTION &quot;saveUser&quot;(&quot;pUserID&quot; integer, &quot;pName&quot; character
    varying, &quot;pLastName&quot; character varying, &quot;pUserName&quot; character varying, 
    &quot;pPassword&quot; character varying, &quot;peMail&quot; character varying)
    RETURNS boolean AS
    $BODY$
    BEGIN
    SELECT 1
    FROM &quot;USERS&quot;
    WHERE &quot;userID&quot; = $1;

    IF FOUND THEN
  	UPDATE &quot;USERS&quot; 
	    SET 	&quot;name&quot; = $2,
		&quot;lastName&quot; = $3,
		&quot;userName&quot; = $4,
		&quot;password&quot; = $5,
		&quot;eMail&quot; = $6
	WHERE &quot;userID&quot; = $1;
    ELSE
	    INSERT INTO &quot;USERS&quot;
	    (&quot;name&quot;, &quot;lastName&quot;, &quot;userName&quot;, &quot;password&quot;, &quot;eMail&quot;)
	    VALUES
    	    ($2, $3, $4, $5, $6);
    END IF;
    END;$BODY$
      LANGUAGE &#39;plpgsql&#39; VOLATILE
      COST 100;
    ALTER FUNCTION &quot;saveUser&quot;(integer, character varying, character varying, character varying, character varying, character varying) OWNER TO postgres;


PostreSQL Documentation states that to call a function which does not return any resultset, it is sufficient to write only its name and properties. So I try to call the function like this:

    &quot;saveUser&quot;(3, &#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;);

But I get the error below:

    ERROR:  syntax error at or near &quot;&quot;saveUser&quot;&quot;
    LINE 1: &quot;saveUser&quot;(3, &#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;,&#39;asd&#39;)
         ^

    ********** Error **********

    ERROR: syntax error at or near &quot;&quot;saveUser&quot;&quot;
    SQL state: 42601
    Character: 1

I have other functions which return a resultset. I use `SELECT * FROM &quot;fnc&quot;(...)` to call them and it works. Why am I getting this error? 


----------
**EDIT:** I am using pgAdmin III Query tool and trying to execute the SQL Statements there.

How to call a function, PostgreSQL

If I have a column names called `category_id` and `Category_Id`, are they different?

And if I have table called `category` and `Category`, are they different?

 

Are column and table name case sensitive in MySQL?

<p>If I have a column names called <code>category_id</code> and <code>Category_Id</code>, are they different?</p>
<p>And if I have table called <code>category</code> and <code>Category</code>, are they different?</p>


I got the following error from a MySQL query.

`#126 - Incorrect key file for table`

I have not even declared a key for this table, but I do have indices.  Does anyone know what could be the problem?

MySQL: #126 - Incorrect key file for table

I was thinking of using TIMESTAMP to store the date+time, but I read that there is a limitation of year 2038 on it. Instead of asking my question in bulk, I preferred to break it up into small parts so that it is easy for novice users to understand as well. So my question(s):

1. What exactly is the Year 2038 problem?
2. Why does it occur and what happens when it occurs?
3. How do we solve it?
4. Are there any possible alternatives to using it, which do not pose a similar problem?
5. What can we do to the existing applications that use TIMESTAMP, to avoid the so-called problem, when it really occurs?

Thanks in advance.

PHP &amp; mySQL: Year 2038 Bug: What is it? How to solve it?

I&#39;ve got a messages table in MySQL which records messages between users. Apart from the typical ids and message types (all integer types) I need to save the actual message text as either VARCHAR or TEXT. I&#39;m setting a front-end limit of 3000 characters which means the messages would never be inserted into the db as longer than this.

Is there a rationale for going with either VARCHAR(3000) or TEXT? There&#39;s something about just writing VARCHAR(3000) that feels somewhat counter-intuitive. I&#39;ve been through other similar posts on Stack Overflow but would be good to get views specific to this type of common message storing.


MySQL: Large VARCHAR vs. TEXT?

I want to return all records that were added to the database within the last 30 days.  I need to convert the date to mm/dd/yy because of display purposes.  

    create_date between DATE_FORMAT(curdate(),&#39;%m/%d/%Y&#39;) AND (DATE_FORMAT(curdate() - interval 30 day,&#39;%m/%d/%Y&#39;)) 

My statement fails to limit the records to the last 30 days - it selects all the records.

Can anyone point me in the right direction?  It feels like I am close.

Thanks and have a great week.

MySQL Query - Records between Today and Last 30 Days

I have a MySQL table for which I do very frequent `SELECT x, y, z FROM table WHERE x LIKE &#39;%text%&#39; OR y LIKE &#39;%text%&#39; OR z LIKE &#39;%text%&#39;` queries. Would any kind of index help speed things up?

There are a few million records in the table. If there is anything that would speed up the search, would it seriously impact disk usage by the database files and the speed of `INSERT` and `DELETE` statements? (no `UPDATE` is ever performed)

&lt;b&gt;Update&lt;/b&gt;: Quickly after posting, I have seen a lot of information and discussion about the way `LIKE` is used in the query; I would like to point out that the solution &lt;b&gt;must&lt;/b&gt; use `LIKE &#39;%text%&#39;` (that is, the text I am looking for is prepended and appended with a % wildcard). The database also has to be local, for many reasons, including security.

How to speed up SELECT .. LIKE queries in MySQL on multiple columns?

I know, I know with what I wrote in the question I shouldn&#39;t be surprised.  But my situation is slowly working on an inherited POS system and my predecessor apparently wasn&#39;t aware of JOINs so when I looked into one of the internal pages that loads for 60 seconds I see that it&#39;s a fairly quick, rewrite these 8 queries as one query with JOINs situation.  Problem is that besides not knowing about JOINs he also seems to have had a fetish for multiple databases and surprise, surprise they use different collations.  Fact of the matter is we use all &quot;normal&quot; latin characters that English speaking people would consider the entire alphabet and this whole thing will be out of use in a few months so a bandaid is all I need.

Long story short is I need some kind of method to cast to a single collation so I can compare two fields from two databases.

Exact error is:

&gt; Cannot resolve the collation conflict
&gt; between
&gt; &quot;SQL_Latin1_General_CP850_CI_AI&quot; and
&gt; &quot;SQL_Latin1_General_CP1_CI_AS&quot; in the
&gt; equal to operation.

Doing a join across two databases with different collations on SQL Server and getting an error

I&#39;m trying to figure out what collation I should be using for various types of data. 100% of the content I will be storing is user-submitted.

My understanding is that I should be using UTF-8 General CI (Case-Insensitive) instead of UTF-8 Binary. However, I can&#39;t find a clear a distinction between UTF-8 General CI and UTF-8 Unicode CI.

1. Should I be storing user-submitted content in UTF-8 General or UTF-8 Unicode CI columns?
2. What type of data would UTF-8 Binary be applicable to?

UTF-8: General? Bin? Unicode?

I&#39;m looking to compare two varchars in SQL, one would be something like `Cafe` and the other `Caf&#233;` is there a way in SQL that will allow the two values to be compared. For instance:

    SELECT *
    FROM Venue
    WHERE Name Like &#39;%cafe%&#39;

So if there is a venue with the name `Big Bobs Caf&#233; Extraordinaire` it would be included in the result set?

How do I perform an accent insensitive compare (e with &#232;, &#233;, &#234; and &#235;) in SQL Server?

Am getting the below error when trying to do a select through a stored procedure in MySQL.

&gt; Illegal mix of collations (latin1_general_cs,IMPLICIT) and (latin1_general_ci,IMPLICIT) for operation &#39;=&#39;

Any idea on what might be going wrong here?

The collation of the table is `latin1_general_ci` and that of the column in the where clause is `latin1_general_cs`.

Troubleshooting &quot;Illegal mix of collations&quot; error in mysql

How can I see what collation a table has? I.E. I want to see:

    +-----------------------------+
    |  table  |     collation     |
    |-----------------------------|
    | t_name  |  latin_general_ci |
    +-----------------------------+


mysql check collation of a table

I&#39;m trying to use &quot;contains&quot; case insensitively. I tried using the solution at the following stackoverflow question, but it didn&#39;t work:

https://stackoverflow.com/questions/187537/is-there-a-case-insensitive-jquery-contains-selector/187557#187557

*For convenience, the solution is copied here:*

    jQuery.extend(
            jQuery.expr[&#39;:&#39;], { 
                    Contains : &quot;jQuery(a).text().toUpperCase().indexOf(m[3].toUpperCase())&gt;=0&quot; 
    });


*Here is the error:*

    Error: q is not a function
    Source File: /js/jquery-1.4.js?ver=1.4
    Line: 81

*Here&#39;s where I&#39;m using it:*

      $(&#39;input.preset&#39;).keyup(function() {
        $(this).next().find(&quot;li&quot;).removeClass(&quot;bold&quot;);
        var theMatch = $(this).val();
        if (theMatch.length &gt; 1){
          theMatch = &quot;li:Contains(&#39;&quot; + theMatch + &quot;&#39;)&quot;;
          $(this).next().find(theMatch).addClass(&quot;bold&quot;);
        }
      });

My use of the original case sensitive &quot;contains&quot; in the same scenario works without any errors. Does anyone have any ideas? I&#39;d appreciate it.


How do I make jQuery Contains case insensitive, including jQuery 1.8+?

I&#39;m not trying to start an argument here, but for whatever reason, it&#39;s typically stated that Visual Basic is case insensitive and C languages aren&#39;t (and somehow that is a good thing).

But here&#39;s my question: Where exactly is Visual Basic case insensitive? When I type...

    Dim ss As String
    Dim SS As String

...into the [Visual&amp;nbsp;Studio&amp;nbsp;2008][6] or [Visual Studio 2010][8] IDE, the second one has a warning of &quot;*Local variable `SS` is already declared in the current block*&quot;. In the VBA VBE, it doesn&#39;t immediately kick an error, but rather just auto-corrects the case.

Am I missing something here with this argument that Visual Basic is not case sensitive? (Also, if you know or care to answer, why would that be a bad thing?)

***Why am I even asking this question?***

I&#39;ve used Visual Basic in many of its
dialects for years now, sometimes as
a hobbyist, sometimes for small
business-related programs in a
workgroup. As of the last six months,
I&#39;ve been working on a big project,
much bigger than I anticipated. Much
of the sample source code out there
is in C#. I don&#39;t have any burning
desire to learn C#, but if there are
things I&#39;m missing out on that C#
offers that Visual Basic doesn&#39;t (an opposite
would be VB.NET offers [XML Literals][3]), then I&#39;d like to know
more about that feature. So in this
case, it&#39;s often argued that C
languages are case sensitive and
that&#39;s good and Visual Basic is case
insensitive and that is bad. I&#39;d
like to know...

 1. How exactly is Visual Basic
        case insensitive since every
        single example in the code editor
        becomes case sensitive (meaning
        the case gets corrected) whether I want
        it or not.
 2. Is this compelling enough for me to
    consider moving to C# if VB.NET case
    is somehow limiting what I could do
    with code?

  [3]: http://en.wikipedia.org/wiki/XML_Literals
  [6]: http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_2008
  [8]: http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_2010


Is VB really case insensitive?

While I found similar [question][1] I didn&#39;t find an answer to my problem

When I try to rename the directory from FOO to foo via `git mv FOO foo` I get  

    fatal: renaming &#39;FOO&#39; failed: Invalid argument

OK. So I try `git mv FOO foo2 &amp;&amp; git mv foo2 foo`

But when I try to commit via `git commit .` I get

    # On branch master
    # Untracked files:
    #   (use &quot;git add &lt;file&gt;...&quot; to include in what will be committed)
    #
    # foo
    nothing added to commit but untracked files present (use &quot;git add&quot; to track)

When I add the directory via `git add foo` nothing changes and `git commit .` gives me the same message again. 

What am I doing wrong? I thought I&#39;m using a case-sensitive system (OSX) why can&#39;t I simply rename the directory?


  [1]: https://stackoverflow.com/questions/1596653/how-to-change-case-of-a-file-in-git-under-cygwin

git mv and only change case of directory

In Java, when doing a replaceAll to look for a regex pattern like:

    replaceAll(&quot;\\?i\\b(\\w+)\\b(\\s+\\1)+\\b&quot;, &quot;$1&quot;); 

(to remove duplicate consecutive case-insensitive words, e.g. Test test), I&#39;m not sure where I put the `?i`.  I read that it is supposed to be at the beginning, but if I take it out then i catch duplicate consecutive words (e.g. test test), but not case-insensitive words (e.g. Test test).  So I thought I could add the ?i in the beginning but that does not seem to get the job done.  Any thoughts?  Thanks!

Is Java RegEx case-insensitive?

The default behaviour of `LIKE` and the other comparison operators, `=` etc is case-sensitive.

Is it possible make them case-insensitive?

Content Type	Original Author	Original Content on Stackoverflow
Question	shin	View Question on Stackoverflow
Solution 1 - Mysql	Seva Alekseyev	View Answer on Stackoverflow
Solution 2 - Mysql	Anitha.y	View Answer on Stackoverflow
Solution 3 - Mysql	Pekka	View Answer on Stackoverflow
Solution 4 - Mysql	Thomas Touzimsky	View Answer on Stackoverflow

Are column and table name case sensitive in MySQL?

Mysql Problem Overview

Mysql Solutions

Solution 1 - Mysql

Solution 2 - Mysql

Solution 3 - Mysql

Solution 4 - Mysql

How to call a function, PostgreSQL

Is JVM open source code?

Attributions