Add chainquery dependencies for Spee.ch, does not include migrations #593
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
BOOLEAN,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
DATE,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
DECIMAL,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
INTEGER,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
STRING,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
TEXT,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
}) => sequelize.define(
|
||||
'abnormal_claim',
|
||||
{
|
||||
|
@ -21,7 +26,7 @@ export default (sequelize, {
|
|||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
set() { },
|
||||
},
|
||||
is_update: {
|
||||
type: INTEGER,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
type: BOOLEAN,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
set() { },
|
||||
},
|
||||
block_hash: {
|
||||
|
@ -49,11 +54,11 @@ export default (sequelize, {
|
|||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
type: DATE(6),
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
type: DATE(6),
|
||||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
||||
set() { },
|
||||
},
|
||||
},
|
||||
|
|
|||
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
![]() These are timestamps, is it ok to create it as an integer? These are timestamps, is it ok to create it as an integer?
![]() This will work for now, I need to verify that This will work for now, I need to verify that `Sequelize.DATE(6)` is fully compatible first.
There's a few things like `INT(1)` that I'm using `INTEGER` for as well that could probably be switched to `Sequelize.BOOLEAN`. I know there's a number of `BIGINT` as well that I need to adjust.
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
BOOLEAN,
|
||||
DATE,
|
||||
DECIMAL,
|
||||
INTEGER,
|
||||
STRING,
|
||||
TEXT,
|
||||
}) => sequelize.define(
|
||||
'address',
|
||||
{
|
||||
|
@ -17,15 +22,15 @@ export default (sequelize, {
|
|||
set() { },
|
||||
},
|
||||
first_seen: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
},
|
||||
|
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
BOOLEAN,
|
||||
DATE,
|
||||
DECIMAL,
|
||||
INTEGER,
|
||||
STRING,
|
||||
TEXT,
|
||||
}) => sequelize.define(
|
||||
'block',
|
||||
{
|
||||
|
@ -81,11 +86,11 @@ export default (sequelize, {
|
|||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
},
|
||||
|
|
|
@ -35,7 +35,12 @@ const getterMethods = {
|
|||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
BOOLEAN,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
DATE,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
DECIMAL,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
INTEGER,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
STRING,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
TEXT,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
}) => sequelize.define(
|
||||
'claim',
|
||||
{
|
||||
|
@ -121,7 +126,7 @@ export default (sequelize, {
|
|||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
is_nsfw: {
|
||||
type: INTEGER,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
type: BOOLEAN,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
language: {
|
||||
|
@ -145,7 +150,7 @@ export default (sequelize, {
|
|||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
is_filtered: {
|
||||
type: INTEGER,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
type: BOOLEAN,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
bid_state: {
|
||||
|
@ -153,11 +158,11 @@ export default (sequelize, {
|
|||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
type: DATE(6),
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
type: DATE(6),
|
||||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
||||
set() { },
|
||||
},
|
||||
fee_address: {
|
||||
|
|
|||
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
![]() This is a boolean that is a This is a boolean that is a `TINYINT(1)` in the database.
![]() This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? This is also an enumeration. I see that you set an enumeration above. Should this be listed as well? `Active,Expired,Controlling,Spent,Accepted` are the enumerations.
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
BOOLEAN,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
DATE,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
DECIMAL,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
INTEGER,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
STRING,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
TEXT,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
}) => sequelize.define(
|
||||
'input',
|
||||
{
|
||||
|
@ -25,7 +30,7 @@ export default (sequelize, {
|
|||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
is_coinbase: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
type: BOOLEAN,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
coinbase: {
|
||||
|
@ -37,7 +42,7 @@ export default (sequelize, {
|
|||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
prevout_n: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
type: INTEGER.UNSIGNED,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
prevout_spend_updated: {
|
||||
|
@ -61,11 +66,11 @@ export default (sequelize, {
|
|||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
created: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
type: DATE(6),
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
modified: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
type: DATE(6),
|
||||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
||||
set() { },
|
||||
},
|
||||
},
|
||||
|
|
|||
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
![]() boolean boolean
![]() this is unsigned. Does it matter that you treat it as just an integer? this is unsigned. Does it matter that you treat it as just an integer?
![]() Ha, alright! I didn't realize
Ha, alright! I didn't realize `TINYINT(1)` is exactly the same as `BOOL`
https://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html
> **BOOL, BOOLEAN**
> These types are synonyms for TINYINT(1). A value of zero is considered false. Nonzero values are considered true
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
![]() boolean boolean
![]() boolean boolean
|
||||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
![]() boolean boolean
|
||||
BOOLEAN,
|
||||
![]() boolean boolean
|
||||
DATE,
|
||||
![]() boolean boolean
|
||||
DECIMAL,
|
||||
![]() boolean boolean
|
||||
INTEGER,
|
||||
![]() boolean boolean
|
||||
STRING,
|
||||
![]() boolean boolean
|
||||
TEXT,
|
||||
![]() boolean boolean
|
||||
}) => sequelize.define(
|
||||
'output',
|
||||
{
|
||||
|
@ -49,7 +54,7 @@ export default (sequelize, {
|
|||
![]() boolean boolean
![]() boolean boolean
|
||||
set() { },
|
||||
},
|
||||
is_spent: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
|
||||
type: BOOLEAN,
|
||||
![]() boolean boolean
|
||||
set() { },
|
||||
},
|
||||
spent_by_input_id: {
|
||||
|
@ -57,11 +62,11 @@ export default (sequelize, {
|
|||
![]() boolean boolean
![]() boolean boolean
|
||||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
|
||||
type: DATE(6),
|
||||
![]() boolean boolean
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
![]() boolean boolean
|
||||
type: DATE(6),
|
||||
![]() boolean boolean
|
||||
set() { },
|
||||
},
|
||||
claim_id: {
|
||||
|
|
|||
![]() boolean boolean
![]() boolean boolean
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
BOOLEAN,
|
||||
DATE,
|
||||
DECIMAL,
|
||||
INTEGER,
|
||||
STRING,
|
||||
TEXT,
|
||||
}) => sequelize.define(
|
||||
'support',
|
||||
{
|
||||
|
@ -33,11 +38,11 @@ export default (sequelize, {
|
|||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
},
|
||||
|
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
BOOLEAN,
|
||||
DATE,
|
||||
DECIMAL,
|
||||
INTEGER,
|
||||
STRING,
|
||||
TEXT,
|
||||
}) => sequelize.define(
|
||||
'transaction_address',
|
||||
{
|
||||
|
|
|
@ -3,7 +3,12 @@ const getterMethods = {
|
|||
}
|
||||
|
||||
export default (sequelize, {
|
||||
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
|
||||
BOOLEAN,
|
||||
DATE,
|
||||
DECIMAL,
|
||||
INTEGER,
|
||||
STRING,
|
||||
TEXT,
|
||||
}) => sequelize.define(
|
||||
'transaction',
|
||||
{
|
||||
|
@ -45,7 +50,7 @@ export default (sequelize, {
|
|||
set() { },
|
||||
},
|
||||
lock_time: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
raw: {
|
||||
|
@ -53,15 +58,15 @@ export default (sequelize, {
|
|||
set() { },
|
||||
},
|
||||
created_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
modified_at: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() { },
|
||||
},
|
||||
created_time: {
|
||||
type: INTEGER,
|
||||
type: DATE(6),
|
||||
set() {},
|
||||
},
|
||||
},
|
||||
|
|
|
@ -88,8 +88,6 @@ module.exports = function (req, res) {
|
|||
res.send((0, _renderFullPage.default)(helmet, html, preloadedState));
|
||||
};
|
||||
|
||||
console.log(httpContext.get('routePath'), runSaga, httpContext.get('routeData'), action, saga);
|
||||
|
||||
if (runSaga) {
|
||||
// create and apply middleware
|
||||
var sagaMiddleware = (0, _reduxSaga.default)();
|
||||
|
|
These are timestamps, is it ok to create it as an integer?