From the docs on LEN (Transact-SQL): Returns the number of characters of the specified string expression, excluding trailing blanks. To return the number of bytes used to represent an expression, use the DATALENGTH function Also, from the support page on How SQL Server Compares Strings with Trailing Spaces: SQL Server follows the ANSI/ISO SQL-92 specification … Read more
To answer the question, on disk MySql uses 1 + the size that is used in the field to store the data (so if the column was declared varchar(45), and the field was “FooBar” it would use 7 bytes on disk, unless of course you where using a multibyte character set, where it would be … Read more
I was thinking you could use a regexp_like condition and use the regular expression to find any non-numerics. I hope this might help?! SELECT * FROM table_with_column_to_search WHERE REGEXP_LIKE(varchar_col_with_non_numerics, ‘[^0-9]+’);
Big integers aren’t actually limited to 20 digits, they’re limited to the numbers that can be expressed in 64 bits (for example, the number 99,999,999,999,999,999,999 is not a valid big integer despite it being 20 digits long). The reason you have this limitation is that native format integers can be manipulated relatively fast by the … Read more
The “length” of the VARCHAR is not the length of the contents, it is the maximum length of the contents. The max length of a VARCHAR is not dynamic, it is fixed and therefore has to be specified. If you don’t want to define a maximum size for it then use VARCHAR(MAX).
select column_name, data_type, character_maximum_length from information_schema.columns where table_name=”myTable”
It depends on how you format the Guid: Guid.NewGuid().ToString() = 36 characters (Hyphenated) outputs: 12345678-1234-1234-1234-123456789abc Guid.NewGuid().ToString(“D”) = 36 characters (Hyphenated, same as ToString()) outputs: 12345678-1234-1234-1234-123456789abc Guid.NewGuid().ToString(“N”) = 32 characters (Digits only) outputs: 12345678123412341234123456789abc Guid.NewGuid().ToString(“B”) = 38 characters (Braces) outputs: {12345678-1234-1234-1234-123456789abc} Guid.NewGuid().ToString(“P”) = 38 characters (Parentheses) outputs: (12345678-1234-1234-1234-123456789abc) Guid.NewGuid().ToString(“X”) = 68 characters (Hexadecimal) outputs: {0x12345678,0x1234,0x1234,{0x12,0x34,0x12,0x34,0x56,0x78,0x9a,0xbc}}
Looks like mysql is case insensitive by default: You probably need to create the column with a case sensitive collation (e.g. utf8_bin): CREATE TABLE WORDS ( ID BIGINT AUTO_INCREMENT, WORD VARCHAR(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL UNIQUE, PRIMARY KEY(ID) );
You can disable STRICT_TRANS_TABLES and STRICT_ALL_TABLES. This allows the automatic truncation of the inserted string. Quote from MySQL Documentation. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. A value can be invalid for several reasons. For example, it might have the wrong data type for … Read more
Sept 2021 edit: I’ve been using MySQL 8.0 for a couple years now, so here’s some updated info. The MySQL manual now has a very informative page regarding conversion between utf8mb3 (currently also known as utf8) and utf8mb4. utf8mb3 is deprecated and will be removed eventually; and when it is removed, its current alias, utf8, … Read more