Have a shared server and running a mysql trigger in which time is being inserted into a column as follows -
Insert INTO mytable SET time=now();
The table and the column time then gets a GMT time.
I want that local time is inserted into that table and column.
Tried this code but still giving GMT time on insertion -
set #localtime = CONVERT_TZ('now()','GMT','+5:30');
Insert INTO mytable SET time=#localtime;
The column time has settings of TIMESTAMP as default and if I change the settings to Varchar, it gives error - "#1048 - Column 'time' cannot be null"
Please help.
I found answer to this question -
set #localtime = (SELECT CONVERT_TZ('now()','##session.time_zone','+5:30'));
Insert INTO mytable SET time=#localtime;
Related
Say I have a mySQL table of a few columns:
id, name, job, jobUpdatedAt
Whenever specifically the job column changes, I want mySQL to automatically update the timestamp of jobUpdatedAt. (so if only name changes, it does not update)
Is such thing possible?
Thanks
CREATE TRIGGER trigger_name
BEFORE UPDATE
ON table_name
FOR EACH ROW
SET NEW.jobUpdatedAt = CASE WHEN OLD.job = NEW.job
THEN OLD.jobUpdatedAt
ELSE CURRENT_TIMESTAMP
END;
jobUpdatedAt will be renewed only when job is updated by fact.
jobUpdatedAt will be saved if the query should try to update it explicitly.
https://dbfiddle.uk/?rdbms=mysql_8.0&fiddle=1b48bce653eb9a1d778e406fa5af894a
I am working on MySql and I have to set the time-stamp of the one of the field of my column to be 4 days ahead from current time-stamp. I created the triggers for the same.
My timestamp fields are Insert_Time and Bid_Time with Default value set as Current_Timestamp.
My Trigger Query:
CREATE TRIGGER setDefaultDate BEFORE INSERT ON product FOR EACH ROW SET New.Bid_Time = ADDDATE(curdate(), INTERVAL 4 DAY);
I tried inserting the rows into table but trigger seems not working. In both the fields I can see the current timestamp only.
My Insert Query:
insert into test.product (ITEM_NAME,ITEM_DESC,Item_Price, ITEM_QTY,SELLER_FIRSTNAME, SELLER_LASTNAME,EMAIL,SELLER_USERNAME,CATEGORY,GROUP_NAME,Bid,COND ) values ('J.K Rowling','HARRYPOTTER AND MYSTERY ','60','10','sahil','kaw', 'sahil1.kaw#gmail.com', 'sahraw','BOOKS','FICTION','1','NEW');
Is it because I am not providing the timestamp value while inserting.
Please find the screen-print attached for the schema of the tables.
This is mostly speculation, but I'm pretty sure the problem is the fact that bid_time has a default value of timestamp. Such columns are automatically initialized.
Unfortunately, the copious documentation on the subject does not seem to address triggers. However, I could easily imagine that the automatic value over-rides the trigger.
I have a MySQL table which hen created automatically puts a ISO 8601 timestamp into one of the fields. It does this because I have set the default value thought phpMyAdmin to TIMESTAMP.
When I update the field I want to add another timestamp to another field. Obviously I cant do that using the default option. Is there an SQL command to add a current timestamp to a field? I have had a quick read through the MySQL website but I couldnt find a way to do it...
I also had a look to see if there was a way of generating an ISO8601 timestamp through PHP but I couldnt figure out a way to convert from a PHP/unix timestamp to ISO8601.
Cheers!
MySQL can automatically initialise and/or update a single TIMESTAMP type column within every table to the current time on INSERT and UPDATE. As explained in Automatic Initialization and Updating for TIMESTAMP:
One TIMESTAMP column in a table can have the current timestamp as the default value for initializing the column, as the auto-update value, or both. It is not possible to have the current timestamp be the default value for one column and the auto-update value for another column.
In your case, because you want separate columns to hold the record's initialisation and update times, you will need to set one (or both) of those columns explicitly; one can explicitly set a date/time column to the current date/time in SQL using the NOW() function:
INSERT INTO my_table (created) VALUES (NOW());
UPDATE my_table SET updated = NOW();
One can even use triggers to achieve the automatic behaviour that is not natively provided by MySQL:
CREATE TRIGGER set_init_time AFTER INSERT ON my_table FOR EACH ROW
SET NEW.created = NOW();
CREATE TRIGGER set_updt_time AFTER UPDATE ON my_table FOR EACH ROW
SET NEW.updated = NOW();
I need to keep track of the time a row was inserted into the database, and the time it was last modified.
I tried to create two separate columns, and use CURRENT_TIMESTAMP:
create table def (
id int,
creation timestamp
default CURRENT_TIMESTAMP,
modification timestamp
on update CURRENT_TIMESTAMP
);
However, this produced an error:
ERROR 1293 (HY000): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
What is the best way to do this?
I'm thinking stored procedure, but looking for a standard solution. I'm also concerned with access privileges -- as few programs/things should be able to touch the timestamps as possible.
Although I would prefer MySQL answers, solutions for other RDBMS's are also appreciated!
Ya this is a lame limitation on MySQL. If you are going through an application you can add a time() call for the created_at column, and let the updated_at column use the CURRENT_TIMESTAMP.
$sql = "INSERT INTO my_table SET name = 'Mike', created_at = " . time();
I'd opt to do this on the created_at column as it probably won't be touched as often as the updated_at column.
-- Edit --
Better yet, use MySQL's built in now() function. This way you only need to be concerned with the timezone of the mysql server, and not the timezones of the app server AND the mysql server.
$sql = "INSERT INTO my_table SET name = 'Mike', created_at = NOW()";
You can use a trigger. The application can also set the value, but if do, it will be overwritten by the database.
delimiter //
CREATE TRIGGER def_bef_update BEFORE UPDATE ON def FOR EACH ROW BEGIN
SET NEW.modification = CURRENT_TIMESTAMP;
END//
delimiter ;
You can also use it to check the data and update your modification date only if has important changes.
Hi I would like to set and forget two fields for tracking the date the record was added and also the date the record was last modified in a mySQL database.
I am using "ON UPDATE CURRENT_TIMESTAMP" and was hoping I would just change UPDATE to INSERT.
No luck however. Can anyone give me the heads up on the best way to achieve this? - preferably inside the database itself.
This assumes MySQL 5. Simply add two triggers:
create table foo (a1 INT, created timestamp, updated timestamp) engine=innodb;
DELIMITER |
CREATE TRIGGER foo_created BEFORE INSERT ON foo
FOR EACH ROW BEGIN
SET new.created := now();
SET new.updated := now();
END;
|
CREATE TRIGGER foo_updated BEFORE UPDATE ON foo
FOR EACH ROW BEGIN
SET new.updated := now();
END;
|
DELIMITER ;
insert into foo (a1) values(7);
select * from foo;
update foo set a1=9;
You basically need both columns to be setup as timestamps with default values of CURRENT_TIMESTAMP. Unfortunately, this is not allowed in MySQL:
Error Code: 1293
Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
You can't have two timestamp columns, even though you need one to only have a default value of CURRENT_TIMESTAMP, and the other one to be UPDATE CURRENT_TIMESTAMP, this is still not allowed.
Your best bet here would be to specify as so:
CREATE TABLE `test` (
`addedDate` dateTime,
`lastModified` timestamp on update CURRENT_TIMESTAMP
)
Unfortunately, you'll have to set the 'addedDate' manually on insert using the NOW() function.
mySQL has a NOW() function you can use, see the tutorial at Tutorials Point that can help you put it in place.
You could add a DATETIME column and set it when you create the row of data. That will serve as the date the record was added.
Next, add a TIMESTAMP column:
Automatic updating of the first TIMESTAMP column in a table occurs under any of the following conditions:
You explicitly set the column to NULL.
The column is not specified explicitly in an INSERT or LOAD DATA INFILE statement.
The column is not specified explicitly in an UPDATE statement and some other column changes value. An UPDATE that sets a column to the value it does not cause the TIMESTAMP column to be updated; if you set a column to its current value, MySQL ignores the update for efficiency.
The TIMESTAMP column will take care of your record modified date.