Under mysql variables sql mode STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION has been removed. My server gets auto updated and the Value
STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION returns.
Under Update Preferences Daily Updates has been set to Never Update, Operating System Package update is set to Never Update.
The server (phpmyadmin) gets updated regularly, and shows:
ERROR No 1364 "Field 'coloumn_name' doesn't have a default value"
My server is from Godaddy
Kindly help..
This is a bit odd because the person (or software) that handles your updates should have updated the table structure for you, but it appears to be a pretty easy fix. phpMyAdmin has an optional database that enables advanced features. It sounds like that database structure wasn't updated when the rest of the phpMyAdmin code was updated.
Your situation is a bit odd in that the column_name column hasn't been changed since at least 2009, which basically means whatever version you were running must have been quite outdated.
In the sql folder (or a different folder if your current phpMyAdmin is still quite old, such as scripts or maybe examples), there are various .sql files which can help with updating your installation. You may wish to run create_tables.sql, but that won't always upgrade existing tables so, again depending on the versions involved, you may be better of dropping the table outright and running that script to create them. I don't see anything in the two current upgrade scripts that would affect column_info, so either that change is so old it's been removed or something else odd happened. You may also want to try doing it manually; if you go to edit that column's structure you can add a default of ''.
I have migrated from a server running MySQL version 5.1.73 - Source Distribution to a server running 5.7.16-0ubuntu0.16.04.1 - (Ubuntu). Both servers are still up and running.
However, I'm encountering multiple (maddening) errors on queries that used to work, for example:
(Error #1364) Field 'Settings' doesn't have a default value
What is a fancy way of saying I didn't write the query on insert to include Settings because it didn't need a value yet.
So, I figure I'll go in and ALTER that field and give it a default value. MySQL lovingly tells me
#1101 - BLOB, TEXT, .. column 'Settings' can't have a default value
Thank you, MySQL..
So it looks like I'm going to have to refactor code, but this could take some time. What is the easiest way to make MySQL on the new server emulate 5.1.73?
UPDATE: It appears that one can make a LONGTEXT field be NULL (vs. NOT NULL), and then the default will in effect be null. But one cannot have a default that is "empty" or "blank" on a LONGTEXT or similar field. Lesson I'm learning here, be careful about making a skeleton/bare record entry into the db without referencing certain fields like this explicitly; any non-referenced LONGTEXT field will need to be null - which by the way is a reasonable and logical value vs. blank.
This has to do with the change they made in 5.7 to enforce strict SQL mode by default. The default SQL mode in MySQL 5.7 is: ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION.
See http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-changes for more information.
You might ask, "why don't they make strict mode optional, but leave it off by default?" The answer is, they did—for about 10 years! It was time to make the next step and enforce strict mode by default. It helps bring MySQL into better SQL compliance and compatibility with other standard RDBMS products.
So how can you turn off strict mode to make it act like the previous, more lax SQL mode? It's easy, put this in your /etc/my.cnf:
sql_mode=NO_ENGINE_SUBSTITUTION
You can also enable that change without restarting mysqld:
mysql> SET GLOBAL sql_mode='NO_ENGINE_SUBSTITUTION';
You probably want to keep NO_ENGINE_SUBSTITUTION on. Engine substitution means for example if you declare a table with ENGINE=InnoDB but the InnoDB storage engine is not enabled for some reason, MySQL will create the table but make it MyISAM silently. This is a bad thing to let happen if you intended it to be InnoDB.
i have been working with the JSON COLUMN_CREATE and COLUMN_JSON options in mariaDB. how do i update just one JSON column without having to extract the entire JSON column?
i see that mysql now has a JSON_SET option. is this something that mariaDB will add?
when i first switched over from mysql to mariaDB the documentation seemed to elude to mariaDB being a "drop-in" replacement for mysql.
also, i thought i read initially that if mysql comes out with a new feature, mariaDB will match the feature.
"drop-in replacement" = "marketing". However, it is mostly true.
You have ventured into a very new feature (JSON) of Oracle MySQL, for which MariaDB has not (yet) caught up. I cannot say when (or even 'if') it will catch up in this.
Meanwhile, MariaDB has added a number of features that have not (yet) been adopted by Oracle.
I'm trying to connect to an Informix database with SQLAlchemy. All my tests seem to show the connection is working; however, whenever I try and perform a read of the database I get the error:
DatabaseError: (DatabaseError) SQLCODE -217 in PREPARE:
IX000: Column (current_role) not found in any table in the query (or SLV is undefined).
'select CURRENT_ROLE from systables' ()
Now the database that I am connecting to doesn't have CURRENT_ROLE, so how can I get round this?
My interactive traceback of the error is shown below in a gist:
https://gist.github.com/2157378
The offending line is:
File "build/bdist.linux-i686/egg/sqlalchemy/dialects/informix/base.py", line 593, in _get_default_schema_name
return connection.execute('select CURRENT_ROLE from systables').scalar()
Is there any workaround for this problem?
I am now led to believe this is a bug in SQLAlchemy (after talking to users in #sqlalchemy) and I have filed a bug report:
http://www.sqlalchemy.org/trac/ticket/2448
You've not identified which version of IBM Informix Dynamic Server (IDS) you are using or which platform you are using it on, so it is hard to help you.
It appears that SQLAlchemy expects a more recent version of Informix than you are using. Somewhat to my surprise, the niladic function CURRENT_ROLE appears to be available in IDS 11.70 (tested on 11.70.FC4 on RHEL 5 for x86/64). It was not recently added, so it will be in any 11.70 version, and possibly in some earlier versions (but not as early as the version you are using).
I'm not sure how much of a bug it is in SQLAlchemy. If the version of Informix that you're using is really old, there is limited virtue in them adding support for it. You can find out which version you're using by running:
SELECT DBINFO('version', 'full')
FROM 'informix'.systables
WHERE tabid = 1;
If that doesn't work, you are many years out of date with your server.
Addendum
Thinking about it a bit more...I wonder what SQLAlchemy is going to do with the role. It probably shouldn't be trying to analyze whether you have permission; it should try an operation and deal with failures. That will be quicker, especially in the common case where you actually do have permission.
There could be two issues:
SQLAlchemy should be aware that some (as yet indeterminate) list of old versions of IDS do not support CURRENT_ROLE.
SQLAlchemy should review why it needs to be aware of the current role.
If you try to create a TEXT column on a table, and give it a default value in MySQL, you get an error (on Windows at least). I cannot see any reason why a text column should not have a default value. No explanation is given by the MySQL documentation. It seems illogical to me (and somewhat frustrating, as I want a default value!). Anybody know why this is not allowed?
Windows MySQL v5 throws an error but Linux and other versions only raise a warning. This needs to be fixed. WTF?
Also see an attempt to fix this as bug #19498 in the MySQL Bugtracker:
Bryce Nesbitt on April 4 2008 4:36pm:
On MS Windows the "no DEFAULT" rule is an error, while on other platforms it is often a warning. While not a bug, it's possible to get trapped by this if you write code on a lenient platform, and later run it on a strict platform:
Personally, I do view this as a bug. Searching for "BLOB/TEXT column can't have a default value" returns about 2,940 results on Google. Most of them are reports of incompatibilities when trying to install DB scripts that worked on one system but not others.
I am running into the same problem now on a webapp I'm modifying for one of my clients, originally deployed on Linux MySQL v5.0.83-log. I'm running Windows MySQL v5.1.41. Even trying to use the latest version of phpMyAdmin to extract the database, it doesn't report a default for the text column in question. Yet, when I try running an insert on Windows (that works fine on the Linux deployment) I receive an error of no default on ABC column. I try to recreate the table locally with the obvious default (based on a select of unique values for that column) and end up receiving the oh-so-useful BLOB/TEXT column can't have a default value.
Again, not maintaining basic compatability across platforms is unacceptable and is a bug.
How to disable strict mode in MySQL 5 (Windows):
Edit /my.ini and look for line
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
Replace it with
sql_mode='MYSQL40'
Restart the MySQL service (assuming that it is mysql5)
net stop mysql5
net start mysql5
If you have root/admin access you might be able to execute
mysql_query("SET ##global.sql_mode='MYSQL40'");
Without any deep knowledge of the mySQL engine, I'd say this sounds like a memory saving strategy. I assume the reason is behind this paragraph from the docs:
Each BLOB or TEXT value is represented internally by a separately allocated object. This is in contrast to all other data types, for which storage is allocated once per column when the table is opened.
It seems like pre-filling these column types would lead to memory usage and performance penalties.
As the main question:
Anybody know why this is not allowed?
is still not answered, I did a quick search and found a relatively new addition from a MySQL developer at MySQL Bugs:
[17 Mar 2017 15:11] Ståle Deraas
Posted by developer:
This is indeed a valid feature request, and at first glance it might seem trivial to add. But TEXT/BLOBS values are not stored directly in the record buffer used for reading/updating tables. So it is a bit more complex to assign default values for them.
This is no definite answer, but at least a starting point for the why question.
In the mean time, I'll just code around it and either make the column nullable or explicitly assign a (default '') value for each insert from the application code...
"Support for DEFAULT in TEXT/BLOB columns"
is a
feature request in the MySQL Bugtracker (Bug #21532).
I see I'm not the only one who would like to put a default value in a TEXT column.
I think this feature should be supported in a later version of MySQL.
This can't be fixed in the version 5.0 of MySQL,
because apparently it would cause incompatibility and dataloss if anyone tried to transfer a database back and forth between the (current) databases that don't support that feature and any databases that did support that feature.
You can get the same effect as a default value by using a trigger
create table my_text
(
abc text
);
delimiter //
create trigger mytext_trigger before insert on my_text
for each row
begin
if (NEW.abc is null ) then
set NEW.abc = 'default text';
end if;
end
//
delimiter ;
Support for using expression as default values was added to MySQL 8.0.13, released 2018-10-22, and works for TEXT, JSON, BLOB and GEOMETRY.
You still cannot write :
create table foo(bar text default 'baz')
But you can now write:
create table foo(bar text default ('baz'))
Which achieve the same thing.
I normally run sites on Linux, but I also develop on a local Windows machine. I've run into this problem many times and just fixed the tables when I encountered the problems. I installed an app yesterday to help someone out and of course ran into the problem again. So, I decided it was time to figure out what was going on - and found this thread. I really don't like the idea of changing the sql_mode of the server to an earlier mode (by default), so I came up with a simple (me thinks) solution.
This solution would of course require developers to wrap their table creation scripts to compensate for the MySQL issue running on Windows. You'll see similar concepts in dump files. One BIG caveat is that this could/will cause problems if partitioning is used.
// Store the current sql_mode
mysql_query("set #orig_mode = ##global.sql_mode");
// Set sql_mode to one that won't trigger errors...
mysql_query('set ##global.sql_mode = "MYSQL40"');
/**
* Do table creations here...
*/
// Change it back to original sql_mode
mysql_query('set ##global.sql_mode = #orig_mode');
That's about it.
For Ubuntu 16.04:
How to disable strict mode in MySQL 5.7:
Edit file /etc/mysql/mysql.conf.d/mysqld.cnf
If below line exists in mysql.cnf
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
Then Replace it with
sql_mode='MYSQL40'
Otherwise
Just add below line in mysqld.cnf
sql_mode='MYSQL40'
This resolved problem.
This is a very old question but still it doesn't seems to have been answered properly. And, my this answer isn't actual answer to the question - "WHY can't a text column have a default value", but as it isn't possible to write long text in comment, and as my comment could help someone to prevent the error, here it is as a separate answer:
Some are saying that the error is occurring because of OS - Windows-Linux; but this isn't directly related to OS. (However, there may be differences in default settings of MySQL within different installers for different OSes, I am not sure.)
The main reason is the flag STRICT_TRANS_TABLES for sql_mode setting. if a value is not specified in INSERT statement for TEXT datatype column and if the flag exist in the sql_mode setting then MySQL is reporting an error; and if the flag doesn't exist then MySQL is only reporting a warning and inserts the record.
So, to prevent this error, one can remove the STRICT_TRANS_TABLES from sql_mode setting of MySQL. (He my need to reset the mode to the previous value if it can affect other operations on the database.)
According to the documentation of SQL mode in MySQL ...
For STRICT_TRANS_TABLES, MySQL converts an invalid value to the closest valid value for the column and inserts the adjusted value. If a value is missing, MySQL inserts the implicit default value for the column data type. In either case, MySQL generates a warning rather than an error and continues processing the statement. Implicit defaults are described in Section 11.6, “Data Type Default Values”.
... and documentation of Data Type Default Values ...
The BLOB, TEXT, GEOMETRY, and JSON data types cannot be assigned a default value.
... TEXT column can not have a default value, but if STRICT_TRANS_TABLES is removed from sql_mode then MySQL inserts empty string '' if no value is specified for TEXT column in INSERT statement.