Laravel overflow when updating value
up vote
0
down vote
favorite
The problem I encountered was I have a column named "timeStart" to store the unix epoch time in millisecond. When I was updating through Laravel update function, the value stored in database shows that it's negative instead of the value I wanted it to store.
e.g. value intended to store: 1540090500000
value stored in database: -1802759264
I'm using bigint datatype here. The same code works on my localhost database but not when I uploaded it onto my shared hosting server, which is a weird issue. What can be done to address this issue?
laravel laravel-5
asked Nov 9 at 7:53
jiale1029
11
|
show 2 more comments
up vote
0
down vote
favorite
The problem I encountered was I have a column named "timeStart" to store the unix epoch time in millisecond. When I was updating through Laravel update function, the value stored in database shows that it's negative instead of the value I wanted it to store.
e.g. value intended to store: 1540090500000
value stored in database: -1802759264
I'm using bigint datatype here. The same code works on my localhost database but not when I uploaded it onto my shared hosting server, which is a weird issue. What can be done to address this issue?
laravel laravel-5
asked Nov 9 at 7:53
jiale1029
11
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The problem I encountered was I have a column named "timeStart" to store the unix epoch time in millisecond. When I was updating through Laravel update function, the value stored in database shows that it's negative instead of the value I wanted it to store.
e.g. value intended to store: 1540090500000
value stored in database: -1802759264
I'm using bigint datatype here. The same code works on my localhost database but not when I uploaded it onto my shared hosting server, which is a weird issue. What can be done to address this issue?
laravel laravel-5
asked Nov 9 at 7:53
jiale1029
11
The problem I encountered was I have a column named "timeStart" to store the unix epoch time in millisecond. When I was updating through Laravel update function, the value stored in database shows that it's negative instead of the value I wanted it to store.
e.g. value intended to store: 1540090500000
value stored in database: -1802759264
I'm using bigint datatype here. The same code works on my localhost database but not when I uploaded it onto my shared hosting server, which is a weird issue. What can be done to address this issue?
laravel laravel-5
laravel laravel-5
asked Nov 9 at 7:53
jiale1029
11
asked Nov 9 at 7:53
jiale1029
11
asked Nov 9 at 7:53
jiale1029
11
asked Nov 9 at 7:53
jiale1029
11
asked Nov 9 at 7:53
jiale1029
11
11
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29
|
show 2 more comments
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29
|
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
2
down vote
So how can I understod you are using different mysql services .
So to learn more abount 32/64bit based bigint please follow
32/64bit os BIGINT
Also I will suggest you to use string instead of bigint. Some os/operations sometimes conflicts due to type bigint
answered Nov 9 at 9:49
Yur Gasparyan
427311
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
So how can I understod you are using different mysql services .
So to learn more abount 32/64bit based bigint please follow
32/64bit os BIGINT
Also I will suggest you to use string instead of bigint. Some os/operations sometimes conflicts due to type bigint
answered Nov 9 at 9:49
Yur Gasparyan
427311
add a comment |
up vote
2
down vote
So how can I understod you are using different mysql services .
So to learn more abount 32/64bit based bigint please follow
32/64bit os BIGINT
Also I will suggest you to use string instead of bigint. Some os/operations sometimes conflicts due to type bigint
answered Nov 9 at 9:49
Yur Gasparyan
427311
add a comment |
up vote
2
down vote
up vote
2
down vote
So how can I understod you are using different mysql services .
So to learn more abount 32/64bit based bigint please follow
32/64bit os BIGINT
Also I will suggest you to use string instead of bigint. Some os/operations sometimes conflicts due to type bigint
answered Nov 9 at 9:49
Yur Gasparyan
427311
So how can I understod you are using different mysql services .
So to learn more abount 32/64bit based bigint please follow
32/64bit os BIGINT
Also I will suggest you to use string instead of bigint. Some os/operations sometimes conflicts due to type bigint
answered Nov 9 at 9:49
Yur Gasparyan
427311
answered Nov 9 at 9:49
Yur Gasparyan
427311
answered Nov 9 at 9:49
Yur Gasparyan
427311
answered Nov 9 at 9:49
Yur Gasparyan
427311
427311
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53221743%2flaravel-overflow-when-updating-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The value you're converting to epoch is probably a date before 1 jan 1970
– cbaconnier
Nov 9 at 8:09
what type of column?
– Yur Gasparyan
Nov 9 at 8:26
@cbaconnier I converted the time input using strtotime and I checked the output which is correct as well, I was thinking whether it's the problem for datatype, as if I put 1540090500 (second) instead of millisecond, it works perfectly. However, my main problem right now is on my localhost, it was able to store the millisecond format, but on my server, it wasn't able to do so.
– jiale1029
Nov 9 at 9:12
@YurGasparyan BIGINT datatype
– jiale1029
Nov 9 at 9:13
32bit or 64bit ?
– Yur Gasparyan
Nov 9 at 9:29