#case-sensitive

Solution: Is the hostname case sensitive? #answer #it #development

Is the hostname case sensitive?

Is the hostname case sensitive? Is

ping MYHOST

equal to

ping myhost

Does it depend on the DNS used? Are there differences between Win/Mac/Unix systems?

Answer [by BillThor ]: Is the hostname case sensitive?

Names resolved from DNS are case insensitive. This is important to prevent confusion. If it was case sensitive then we would have eight variants of .com…

How to: git mv and only change case of directory

git mv and only change case of directory

While I found similar question I didn’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 'FOO' failed: Invalid argument

OK. So I try git mv FOO foo2 && git mv foo2 foo

But when I try to commit via git commit . I get

# On branch master # Untracked files: # (use "git add ..." to…

How to: Is SQL syntax case sensitive?

Is SQL syntax case sensitive?

Is SQL case sensitive. I’ve used MySQL and SQL Server which both seem to be case in-sensitive. Is this always the case? Does the standard define case-sensitivity?

Answer: Is SQL syntax case sensitive?

This isn’t strictly SQL language, but in SQL Server if your database collation is case-sensitive, then all table names are case-sensitive.

Answer: Is SQL syntax case…

How to: Javascript indexOf case insensitive

Javascript indexOf case insensitive

I have the following:

if (referrer.indexOf("Ral") == -1) { ... }

What I like to do is to make Ral case insensitive, so that it can be RAl, rAl, etc. and still match.

Is there a way to say that Ral has to be case-insensitive?

Answer: Javascript indexOf case insensitive

To do a better search use the following code,

var myFav = "javascript"; var theList =…

By default, the columns/fields for vachar and text type are case insensitive.

This will affect the results of SELECT queries => Although the data is "Goh", it will still be returned for a query that asked for "goh".

If case sensitive is required for a field, it should be defined using Collation ending with _cs.

There was a good question sent to [email protected] last night, so I thought I'd write up the answer here for everyone. The question was "are fiesta addresses case-sensitive?".

In general, the local-part (that's the part before the @ sign) of an email address is case-sensitive. That means that [email protected] is different from [email protected]. The domain (the part after the @ sign) of an address is not case-sensitive, though. So [email protected] is the same address as [email protected]. This is in keeping with the case-insensitivity of DNS names in general.

The same standard that defines the rules above, however, also suggests that email software should preserve but not depend on the case-insensitive nature of addresses (i.e. if you are receiving mail for example.com, you should treat [email protected] and [email protected] as the same address). Fiesta takes that a step further and follows what I'll call the Gmail rules for addresses. That means that the addresses for fiesta lists are completely case-insensitive, and the "." character is ignored in addresses. So [email protected] is the same list as [email protected].

Like Gmail addresses, fiesta list names can contain any letters of the alphabet, any digits, or the '.' character. Fiesta addresses can also contain the '-' and '_' characters, however, and those characters get ignored like the '.' character. Also like Gmail, list names can be up to 30 characters long, but unlike Gmail, there is no minimum.

I pushed out new versions of PGXN::Manager, PGXN::API, and PGXN::Site today, all with the aim of resolving some issues with case-sensitivity. I was alerted to this when Daniele Varrzzo released italian_fts with the Italian tag and the API sync blew up. Oops.

So here's the deal. The following objects have case-insensitive names on PGXN:

Distributions

Extensions

Versions

Users (nickname)

Tags

These names are case-preserving, so they should show up with the proper capitalization in JSON files and whatnot. But to avoid issues with URLs, I decided that all file names should be lowercase only. Fortunately, nearly everything was lowercase already: only a few nickname JSON files were not lowercased, plus the files for pgTAP. So once I got the code updated, I renamed those files appropriately. In the case of the pgTAP download, I actually re-indexed it, so that the prefix in the zip file would properly be "pgtap-0.25.0" instead of "pgTAP-0.25.0", since the file name is now pgtap-0.25.0.pgz.

So why make these objects case-insensitive? Well, because I tend to think of the names of things as having meaning, and really, there is no difference in meaning between "pgtap," "pgTAP," or "PGTap." I've relased pgTAP; I think it would be as confusing as hell if someone else released a completely different distribution named "PGTap." (And I went through a bit of hell when the Apache::test CPAN module was replaced with Apache::Test, a completely new module. It really messed things up on the case-insensitive file system I use).