Add chainquery dependencies for Spee.ch, does not include migrations #593

Merged
skhameneh merged 15 commits from add-chainquery into master 2018-10-10 02:12:18 +02:00
29 changed files with 1539 additions and 3 deletions
Showing only changes of commit a25e736ee1 - Show all commits

View file

@ -0,0 +1,8 @@
{
"host": "localhost",
"port": "3306",
"timeout": 30,
"database": "chainquery",
"username": "lbry",
"password": "root"
}

532
package-lock.json generated
View file

@ -984,6 +984,15 @@
}
}
},
"agent-base": {
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/agent-base/-/agent-base-4.2.1.tgz",
"integrity": "sha512-JVwXMr9nHYTUXsBFKUqhJwvlcYU/blreOEUkhNR2eXZIvwd+c+o5V4MgDPKWnMS/56awN3TRzIP+KoPn+roQtg==",
"dev": true,
"requires": {
"es6-promisify": "5.0.0"
}
},
"ajv": {
"version": "5.5.2",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz",
@ -1079,6 +1088,12 @@
"integrity": "sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==",
"dev": true
},
"arch": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/arch/-/arch-2.1.1.tgz",
"integrity": "sha512-BLM56aPo9vLLFVa8+/+pJLnrZ7QGGTVHWsCwieAWT9o9K8UeGaQbzZbGoabWLOo2ksBCztoXdqBZBplqLDDCSg==",
"dev": true
},
"are-we-there-yet": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz",
@ -1238,6 +1253,12 @@
"integrity": "sha1-NhIfhFwFeBct5Bmpfb6x0W7DRUI=",
"dev": true
},
"async-limiter": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/async-limiter/-/async-limiter-1.0.0.tgz",
"integrity": "sha512-jp/uFnooOiO+L211eZOoSyzpOITMXx1rBITauYykG3BRYPu8h0UcxsPNB04RR5vo4Tyz3+ay17tR6JVf9qzYWg==",
"dev": true
},
"asynckit": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
@ -1914,6 +1935,16 @@
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-1.11.0.tgz",
"integrity": "sha1-RqoXUftqL5PuXmibsQh9SxTGwgU="
},
"bl": {
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/bl/-/bl-1.2.2.tgz",
"integrity": "sha512-e8tQYnZodmebYDWGH7KMRvtzKXaJHx3BbilrgZCfvyLUYdKpK1t5PSPmpkny/SgiTSCnjfLW7v5rlONXVFkQEA==",
"dev": true,
"requires": {
"readable-stream": "2.3.6",
"safe-buffer": "5.1.2"
}
},
"block-stream": {
"version": "0.0.9",
"resolved": "https://registry.npmjs.org/block-stream/-/block-stream-0.0.9.tgz",
@ -2131,6 +2162,35 @@
}
}
},
"buffer-alloc": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/buffer-alloc/-/buffer-alloc-1.2.0.tgz",
"integrity": "sha512-CFsHQgjtW1UChdXgbyJGtnm+O/uLQeZdtbDo8mfUgYXCHSM1wgrVxXm6bSyrUuErEb+4sYVGCzASBRot7zyrow==",
"dev": true,
"requires": {
"buffer-alloc-unsafe": "1.1.0",
"buffer-fill": "1.0.0"
}
},
"buffer-alloc-unsafe": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/buffer-alloc-unsafe/-/buffer-alloc-unsafe-1.1.0.tgz",
"integrity": "sha512-TEM2iMIEQdJ2yjPJoSIsldnleVaAk1oW3DBVUykyOLsEsFmEc9kn+SFFPz+gl54KQNxlDnAwCXosOS9Okx2xAg==",
"dev": true
},
"buffer-crc32": {
"version": "0.2.13",
"resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
"integrity": "sha1-DTM+PwDqxQqhRUq9MO+MKl2ackI=",
"dev": true,
"optional": true
},
"buffer-fill": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/buffer-fill/-/buffer-fill-1.0.0.tgz",
"integrity": "sha1-+PeLdniYiO858gXNY39o5wISKyw=",
"dev": true
},
"buffer-from": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.1.tgz",
@ -2545,6 +2605,33 @@
"resolved": "https://registry.npmjs.org/cli-width/-/cli-width-2.2.0.tgz",
"integrity": "sha1-/xnt6Kml5XkyQUewwR8PvLq+1jk="
},
"clipboardy": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/clipboardy/-/clipboardy-1.2.3.tgz",
"integrity": "sha512-2WNImOvCRe6r63Gk9pShfkwXsVtKCroMAevIbiae021mS850UkWPbevxsBz3tnvjZIEGvlwaqCPsw+4ulzNgJA==",
"dev": true,
"requires": {
"arch": "2.1.1",
"execa": "0.8.0"
},
"dependencies": {
"execa": {
"version": "0.8.0",
"resolved": "https://registry.npmjs.org/execa/-/execa-0.8.0.tgz",
"integrity": "sha1-2NdrvBtVIX7RkP1t1J08d07PyNo=",
"dev": true,
"requires": {
"cross-spawn": "5.1.0",
"get-stream": "3.0.0",
"is-stream": "1.1.0",
"npm-run-path": "2.0.2",
"p-finally": "1.0.0",
"signal-exit": "3.0.2",
"strip-eof": "1.0.0"
}
}
}
},
"cliui": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/cliui/-/cliui-2.1.0.tgz",
@ -3161,6 +3248,138 @@
"resolved": "https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz",
"integrity": "sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU="
},
"decompress": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/decompress/-/decompress-4.2.0.tgz",
"integrity": "sha1-eu3YVCflqS2s/lVnSnxQXpbQH50=",
"dev": true,
"optional": true,
"requires": {
"decompress-tar": "4.1.1",
"decompress-tarbz2": "4.1.1",
"decompress-targz": "4.1.1",
"decompress-unzip": "4.0.1",
"graceful-fs": "4.1.11",
"make-dir": "1.3.0",
"pify": "2.3.0",
"strip-dirs": "2.1.0"
},
"dependencies": {
"pify": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"integrity": "sha1-7RQaasBDqEnqWISY59yosVMw6Qw=",
"dev": true,
"optional": true
}
}
},
"decompress-tar": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/decompress-tar/-/decompress-tar-4.1.1.tgz",
"integrity": "sha512-JdJMaCrGpB5fESVyxwpCx4Jdj2AagLmv3y58Qy4GE6HMVjWz1FeVQk1Ct4Kye7PftcdOo/7U7UKzYBJgqnGeUQ==",
"dev": true,
"requires": {
"file-type": "5.2.0",
"is-stream": "1.1.0",
"tar-stream": "1.6.1"
}
},
"decompress-tarbz2": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/decompress-tarbz2/-/decompress-tarbz2-4.1.1.tgz",
"integrity": "sha512-s88xLzf1r81ICXLAVQVzaN6ZmX4A6U4z2nMbOwobxkLoIIfjVMBg7TeguTUXkKeXni795B6y5rnvDw7rxhAq9A==",
"dev": true,
"optional": true,
"requires": {
"decompress-tar": "4.1.1",
"file-type": "6.2.0",
"is-stream": "1.1.0",
"seek-bzip": "1.0.5",
"unbzip2-stream": "1.2.5"
},
"dependencies": {
"file-type": {
"version": "6.2.0",
"resolved": "https://registry.npmjs.org/file-type/-/file-type-6.2.0.tgz",
"integrity": "sha512-YPcTBDV+2Tm0VqjybVd32MHdlEGAtuxS3VAYsumFokDSMG+ROT5wawGlnHDoz7bfMcMDt9hxuXvXwoKUx2fkOg==",
"dev": true,
"optional": true
}
}
},
"decompress-targz": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/decompress-targz/-/decompress-targz-4.1.1.tgz",
"integrity": "sha512-4z81Znfr6chWnRDNfFNqLwPvm4db3WuZkqV+UgXQzSngG3CEKdBkw5jrv3axjjL96glyiiKjsxJG3X6WBZwX3w==",
"dev": true,
"requires": {
"decompress-tar": "4.1.1",
"file-type": "5.2.0",
"is-stream": "1.1.0"
}
},
"decompress-unzip": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/decompress-unzip/-/decompress-unzip-4.0.1.tgz",
"integrity": "sha1-3qrM39FK6vhVePczroIQ+bSEj2k=",
"dev": true,
"optional": true,
"requires": {
"file-type": "3.9.0",
"get-stream": "2.3.1",
"pify": "2.3.0",
"yauzl": "2.10.0"
},
"dependencies": {
"fd-slicer": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
"integrity": "sha1-JcfInLH5B3+IkbvmHY85Dq4lbx4=",
"dev": true,
"optional": true,
"requires": {
"pend": "1.2.0"
}
},
"file-type": {
"version": "3.9.0",
"resolved": "https://registry.npmjs.org/file-type/-/file-type-3.9.0.tgz",
"integrity": "sha1-JXoHg4TR24CHvESdEH1SpSZyuek=",
"dev": true,
"optional": true
},
"get-stream": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/get-stream/-/get-stream-2.3.1.tgz",
"integrity": "sha1-Xzj5PzRgCWZu4BUKBUFn+Rvdld4=",
"dev": true,
"optional": true,
"requires": {
"object-assign": "4.1.1",
"pinkie-promise": "2.0.1"
}
},
"pify": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
"integrity": "sha1-7RQaasBDqEnqWISY59yosVMw6Qw=",
"dev": true,
"optional": true
},
"yauzl": {
"version": "2.10.0",
"resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
"integrity": "sha1-x+sXyT4RLLEIb6bY5R+wZnt5pfk=",
"dev": true,
"optional": true,
"requires": {
"buffer-crc32": "0.2.13",
"fd-slicer": "1.1.0"
}
}
}
},
"deep-eql": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/deep-eql/-/deep-eql-3.0.1.tgz",
@ -3433,6 +3652,15 @@
"iconv-lite": "0.4.23"
}
},
"end-of-stream": {
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.1.tgz",
"integrity": "sha512-1MkrZNvWTKCaigbn+W15elq2BB/L22nqrSY5DKlo3X6+vclJm8Bb5djXJBmEX6fS3+zCh/F4VBK5Z2KxJt4s2Q==",
"dev": true,
"requires": {
"once": "1.4.0"
}
},
"enhanced-resolve": {
"version": "3.4.1",
"resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-3.4.1.tgz",
@ -3517,6 +3745,23 @@
"event-emitter": "0.3.5"
}
},
"es6-promisify": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/es6-promisify/-/es6-promisify-5.0.0.tgz",
"integrity": "sha1-UQnWLz5W6pZ8S2NQWu8IKRyKUgM=",
"dev": true,
"requires": {
"es6-promise": "4.2.4"
},
"dependencies": {
"es6-promise": {
"version": "4.2.4",
"resolved": "https://registry.npmjs.org/es6-promise/-/es6-promise-4.2.4.tgz",
"integrity": "sha512-/NdNZVJg+uZgtm9eS3O6lrOLYmQag2DjdEXuPaHlZ6RuVqgqaVZfgYCepEIKsLqwdQArOPtC3XzRLqGGfT8KQQ==",
"dev": true
}
}
},
"es6-set": {
"version": "0.1.5",
"resolved": "https://registry.npmjs.org/es6-set/-/es6-set-0.1.5.tgz",
@ -4235,6 +4480,29 @@
}
}
},
"extract-zip": {
"version": "1.6.7",
"resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-1.6.7.tgz",
"integrity": "sha1-qEC0uK9kAyZMjbV/Txp0Mz74H+k=",
"dev": true,
"requires": {
"concat-stream": "1.6.2",
"debug": "2.6.9",
"mkdirp": "0.5.1",
"yauzl": "2.4.1"
},
"dependencies": {
"debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"dev": true,
"requires": {
"ms": "2.0.0"
}
}
}
},
"extsprintf": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.3.0.tgz",
@ -4353,6 +4621,12 @@
}
}
},
"file-type": {
"version": "5.2.0",
"resolved": "https://registry.npmjs.org/file-type/-/file-type-5.2.0.tgz",
"integrity": "sha1-LdvqfHP/42No365J3DOMBYwritY=",
"dev": true
},
"fill-range": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-4.0.0.tgz",
@ -4522,6 +4796,18 @@
"integrity": "sha1-g8YK/Fi5xWmXAH7Rp2izqzA6RP4=",
"dev": true
},
"fs-constants": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs-constants/-/fs-constants-1.0.0.tgz",
"integrity": "sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==",
"dev": true
},
"fs-copy-file-sync": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/fs-copy-file-sync/-/fs-copy-file-sync-1.1.1.tgz",
"integrity": "sha512-2QY5eeqVv4m2PfyMiEuy9adxNP+ajf+8AR05cEi+OAzPcOj90hvFImeZhTmKLBgSd9EvG33jsD7ZRxsx9dThkQ==",
"dev": true
},
"fs-extra": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-5.0.0.tgz",
@ -5280,6 +5566,13 @@
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.1.11.tgz",
"integrity": "sha1-Dovf5NHduIVNZOBOp8AOKgJuVlg="
},
"graceful-readlink": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/graceful-readlink/-/graceful-readlink-1.0.1.tgz",
"integrity": "sha1-TK+tdrxi8C+gObL5Tpo906ORpyU=",
"dev": true,
"optional": true
},
"growl": {
"version": "1.10.5",
"resolved": "https://registry.npmjs.org/growl/-/growl-1.10.5.tgz",
@ -5553,6 +5846,16 @@
"resolved": "https://registry.npmjs.org/https-browserify/-/https-browserify-1.0.0.tgz",
"integrity": "sha1-7AbBDgo0wPL68Zn3/X/Hj//QPHM="
},
"https-proxy-agent": {
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-2.2.1.tgz",
"integrity": "sha512-HPCTS1LW51bcyMYbxUIOO4HEOlQ1/1qRaFWcyxvwaqUS9TY88aoEuHUY33kuAh1YhVVaDQhLZsnPd+XNARWZlQ==",
"dev": true,
"requires": {
"agent-base": "4.2.1",
"debug": "3.1.0"
}
},
"husky": {
"version": "0.14.3",
"resolved": "https://registry.npmjs.org/husky/-/husky-0.14.3.tgz",
@ -5899,6 +6202,13 @@
"ip-regex": "2.1.0"
}
},
"is-natural-number": {
"version": "4.0.1",
"resolved": "https://registry.npmjs.org/is-natural-number/-/is-natural-number-4.0.1.tgz",
"integrity": "sha1-q5124dtM7VHjXeDHLr7PCfc0zeg=",
"dev": true,
"optional": true
},
"is-npm": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-npm/-/is-npm-1.0.0.tgz",
@ -6030,11 +6340,26 @@
"resolved": "https://registry.npmjs.org/is-windows/-/is-windows-1.0.2.tgz",
"integrity": "sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA=="
},
"is-wsl": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-wsl/-/is-wsl-1.1.0.tgz",
"integrity": "sha1-HxbkqiKwTRM2tmGIpmrzxgDDpm0=",
"dev": true
},
"isarray": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-0.0.1.tgz",
"integrity": "sha1-ihis/Kmo9Bd+Cav8YDiTmwXR7t8="
},
"isbinaryfile": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/isbinaryfile/-/isbinaryfile-3.0.3.tgz",
"integrity": "sha512-8cJBL5tTd2OS0dM4jz07wQd5g0dCCqIhUxPIGtZfa5L6hWlvV5MHTITy/DBAsF+Oe2LS1X3krBUhNwaGUWpWxw==",
"dev": true,
"requires": {
"buffer-alloc": "1.2.0"
}
},
"isexe": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
@ -6867,6 +7192,46 @@
"integrity": "sha1-Sr6/7tdUHywnrPspvbvRXI1bpPc=",
"dev": true
},
"ndb": {
"version": "1.0.24",
"resolved": "https://registry.npmjs.org/ndb/-/ndb-1.0.24.tgz",
"integrity": "sha512-GS72oSI/jrI+A/hh+qmGPPav/2+qLeup0txS3SbnFBKkH0KD/WXZhvmTO4LlEXOSV23v7x62EnqcQkrnCk2ZTA==",
"dev": true,
"requires": {
"chokidar": "2.0.4",
"clipboardy": "1.2.3",
"fs-copy-file-sync": "1.1.1",
"isbinaryfile": "3.0.3",
"mime": "2.3.1",
"ndb-node-pty-prebuilt": "0.8.0",
"opn": "5.3.0",
"puppeteer": "1.6.1",
"rimraf": "2.6.2",
"update-notifier": "2.5.0",
"ws": "6.0.0",
"xterm": "3.6.0"
},
"dependencies": {
"mime": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/mime/-/mime-2.3.1.tgz",
"integrity": "sha512-OEUllcVoydBHGN1z84yfQDimn58pZNNNXgZlHXSboxMlFvgI6MXSWpWKpFRra7H1HxpVhHTkrghfRW49k6yjeg==",
"dev": true
}
}
},
"ndb-node-pty-prebuilt": {
"version": "0.8.0",
"resolved": "https://registry.npmjs.org/ndb-node-pty-prebuilt/-/ndb-node-pty-prebuilt-0.8.0.tgz",
"integrity": "sha512-j3XcGQgISib600/12hz56jaFsmpmDdFOKMHRq94+aWkxk0LqoPM5yAeJwacaPLnGm2NRFC3gTUocTIS+GSmQDQ==",
"dev": true,
"optional": true,
"requires": {
"decompress": "4.2.0",
"decompress-targz": "4.1.1",
"nan": "2.10.0"
}
},
"negotiator": {
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/negotiator/-/negotiator-0.6.1.tgz",
@ -10049,6 +10414,15 @@
"mimic-fn": "1.2.0"
}
},
"opn": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/opn/-/opn-5.3.0.tgz",
"integrity": "sha512-bYJHo/LOmoTd+pfiYhfZDnf9zekVJrY+cnS2a5F2x+w5ppvTqObojTP7WiFG+kVZs9Inw+qQ/lw7TroWwhdd2g==",
"dev": true,
"requires": {
"is-wsl": "1.1.0"
}
},
"optimist": {
"version": "0.6.1",
"resolved": "https://registry.npmjs.org/optimist/-/optimist-0.6.1.tgz",
@ -10933,6 +11307,12 @@
"ipaddr.js": "1.8.0"
}
},
"proxy-from-env": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/proxy-from-env/-/proxy-from-env-1.0.0.tgz",
"integrity": "sha1-M8UDmPcOp+uW0h97gXYwpVeRx+4=",
"dev": true
},
"prr": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/prr/-/prr-1.0.1.tgz",
@ -10984,6 +11364,39 @@
"resolved": "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz",
"integrity": "sha1-wNWmOycYgArY4esPpSachN1BhF4="
},
"puppeteer": {
"version": "1.6.1",
"resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.6.1.tgz",
"integrity": "sha512-qz6DLwK+PhlBMjJZOMOsgVCnweYLtmiqnmJYUDPT++ElMz+cQgbsCNKPw4YDVpg3RTbsRX/pqQqr20zrp0cuKw==",
"dev": true,
"requires": {
"debug": "3.1.0",
"extract-zip": "1.6.7",
"https-proxy-agent": "2.2.1",
"mime": "2.3.1",
"progress": "2.0.0",
"proxy-from-env": "1.0.0",
"rimraf": "2.6.2",
"ws": "5.2.2"
},
"dependencies": {
"mime": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/mime/-/mime-2.3.1.tgz",
"integrity": "sha512-OEUllcVoydBHGN1z84yfQDimn58pZNNNXgZlHXSboxMlFvgI6MXSWpWKpFRra7H1HxpVhHTkrghfRW49k6yjeg==",
"dev": true
},
"ws": {
"version": "5.2.2",
"resolved": "https://registry.npmjs.org/ws/-/ws-5.2.2.tgz",
"integrity": "sha512-jaHFD6PFv6UgoIVda6qZllptQsMlDEJkTQcybzzXDYM1XO9Y8em691FGMPmM46WGyLU4z9KMgQN+qrux/nhlHA==",
"dev": true,
"requires": {
"async-limiter": "1.0.0"
}
}
}
},
"q": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/q/-/q-1.5.1.tgz",
@ -11909,6 +12322,28 @@
"source-map": "0.4.4"
}
},
"seek-bzip": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/seek-bzip/-/seek-bzip-1.0.5.tgz",
"integrity": "sha1-z+kXyz0nS8/6x5J1ivUxc+sfq9w=",
"dev": true,
"optional": true,
"requires": {
"commander": "2.8.1"
},
"dependencies": {
"commander": {
"version": "2.8.1",
"resolved": "https://registry.npmjs.org/commander/-/commander-2.8.1.tgz",
"integrity": "sha1-Br42f+v9oMMwqh4qBy09yXYkJdQ=",
"dev": true,
"optional": true,
"requires": {
"graceful-readlink": "1.0.1"
}
}
}
},
"semver": {
"version": "5.5.1",
"resolved": "https://registry.npmjs.org/semver/-/semver-5.5.1.tgz",
@ -12546,6 +12981,16 @@
"resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-3.0.0.tgz",
"integrity": "sha1-IzTBjpx1n3vdVv3vfprj1YjmjtM="
},
"strip-dirs": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/strip-dirs/-/strip-dirs-2.1.0.tgz",
"integrity": "sha512-JOCxOeKLm2CAS73y/U4ZeZPTkE+gNVCzKt7Eox84Iej1LT/2pTWYpZKJuxwQpvX1LiZb1xokNR7RLfuBAa7T3g==",
"dev": true,
"optional": true,
"requires": {
"is-natural-number": "4.0.1"
}
},
"strip-eof": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/strip-eof/-/strip-eof-1.0.0.tgz",
@ -12717,6 +13162,21 @@
"inherits": "2.0.3"
}
},
"tar-stream": {
"version": "1.6.1",
"resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-1.6.1.tgz",
"integrity": "sha512-IFLM5wp3QrJODQFPm6/to3LJZrONdBY/otxcvDIQzu217zKye6yVR3hhi9lAjrC2Z+m/j5oDxMPb1qcd8cIvpA==",
"dev": true,
"requires": {
"bl": "1.2.2",
"buffer-alloc": "1.2.0",
"end-of-stream": "1.4.1",
"fs-constants": "1.0.0",
"readable-stream": "2.3.6",
"to-buffer": "1.1.1",
"xtend": "4.0.1"
}
},
"term-size": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/term-size/-/term-size-1.2.0.tgz",
@ -12806,6 +13266,12 @@
"resolved": "https://registry.npmjs.org/to-arraybuffer/-/to-arraybuffer-1.0.1.tgz",
"integrity": "sha1-fSKbH8xjfkZsoIEYCDanqr/4P0M="
},
"to-buffer": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/to-buffer/-/to-buffer-1.1.1.tgz",
"integrity": "sha512-lx9B5iv7msuFYE3dytT+KE5tap+rNYw+K4jVkb9R/asAb+pbBSM17jtunHplhBe6RRJdZx3Pn2Jph24O32mOVg==",
"dev": true
},
"to-fast-properties": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz",
@ -13021,6 +13487,45 @@
"resolve": "1.8.1"
}
},
"unbzip2-stream": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/unbzip2-stream/-/unbzip2-stream-1.2.5.tgz",
"integrity": "sha512-izD3jxT8xkzwtXRUZjtmRwKnZoeECrfZ8ra/ketwOcusbZEp4mjULMnJOCfTDZBgGQAAY1AJ/IgxcwkavcX9Og==",
"dev": true,
"optional": true,
"requires": {
"buffer": "3.6.0",
"through": "2.3.8"
},
"dependencies": {
"base64-js": {
"version": "0.0.8",
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-0.0.8.tgz",
"integrity": "sha1-EQHpVE9KdrG8OybUUsqW16NeeXg=",
"dev": true,
"optional": true
},
"buffer": {
"version": "3.6.0",
"resolved": "http://registry.npmjs.org/buffer/-/buffer-3.6.0.tgz",
"integrity": "sha1-pyyTb3e5a/UvX357RnGAYoVR3vs=",
"dev": true,
"optional": true,
"requires": {
"base64-js": "0.0.8",
"ieee754": "1.1.12",
"isarray": "1.0.0"
}
},
"isarray": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
"integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
"dev": true,
"optional": true
}
}
},
"undefsafe": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/undefsafe/-/undefsafe-2.0.2.tgz",
@ -13647,9 +14152,6 @@
}
}
},
"winston-slack-webhook": {
"version": "github:billbitt/winston-slack-webhook#ce99792bdf6473a9da69c91772eb4ecec4979b6c"
},
"wkx": {
"version": "0.4.5",
"resolved": "https://registry.npmjs.org/wkx/-/wkx-0.4.5.tgz",
@ -13730,6 +14232,15 @@
"signal-exit": "3.0.2"
}
},
"ws": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/ws/-/ws-6.0.0.tgz",
"integrity": "sha512-c2UlYcAZp1VS8AORtpq6y4RJIkJ9dQz18W32SpR/qXGfLDZ2jU4y4wKvvZwqbi7U6gxFQTeE+urMbXU/tsDy4w==",
"dev": true,
"requires": {
"async-limiter": "1.0.0"
}
},
"x-xss-protection": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/x-xss-protection/-/x-xss-protection-1.1.0.tgz",
@ -13746,6 +14257,12 @@
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.1.tgz",
"integrity": "sha1-pcbVMr5lbiPbgg77lDofBJmNY68="
},
"xterm": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/xterm/-/xterm-3.6.0.tgz",
"integrity": "sha512-D/7/fm7oGzZksLFQdpn1TD63V+T4Ad3LZR2JfZ1QrPZ1yDjKedIKWAZXgzeHQw8S/5HYD08GdkLnjeLm/e6Yog==",
"dev": true
},
"y18n": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz",
@ -13781,6 +14298,15 @@
"integrity": "sha1-1UVjW+HjPFQmScaRc+Xeas+uNN0="
}
}
},
"yauzl": {
"version": "2.4.1",
"resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.4.1.tgz",
"integrity": "sha1-lSj0QtqxsihOWLQ3m7GU4i4MQAU=",
"dev": true,
"requires": {
"fd-slicer": "1.0.1"
}
}
}
}

View file

@ -15,6 +15,8 @@
"prestart": "builder run bundle",
"start": "node server.js",
"start:build": "builder run start",
"devtools:server": "ndb server.js",
"devtools:chainquery": "ndb ./server/chainquery/index.debug.js",
"test": "mocha --recursive",
"test:no-lbc": "npm test -- --grep @usesLbc --invert",
"test:server": "mocha --recursive './server/**/*.test.js'",
@ -108,6 +110,7 @@
"file-loader": "^1.1.11",
"husky": "^0.14.3",
"mocha": "^5.2.0",
"ndb": "^1.0.24",
"node-sass": "^4.9.3",
"nodemon": "^1.17.5",
"redux-devtools": "^3.4.1",

View file

@ -0,0 +1,10 @@
console.log('Loading `chainquery`, please wait...')
require('@babel/polyfill');
require('@babel/register');
const chainquery = require('./');
global.chainquery = chainquery.default ? chainquery.default : chainquery;
console.log('`chainquery` has been loaded into the global context.')

View file

@ -0,0 +1,80 @@
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
const Sequelize = require('sequelize');
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
const logger = require('winston');
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import abnormalClaimTable from './tables/abnormalClaimTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:23:23 +02:00 (Migrated from github.com)
Review

Is this useful to you? This is for claims that were not made through the app. Claims that are not structured according to the lbry protocol.

Is this useful to you? This is for claims that were not made through the app. Claims that are not structured according to the lbry protocol.
skhameneh commented 2018-10-09 20:11:58 +02:00 (Migrated from github.com)
Review

Not at the moment, retained for full functionality if this is to be split out into a separate lib

Not at the moment, retained for full functionality if this is to be split out into a separate lib
import addressTable from './tables/addressTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import applicationStatusTable from './tables/applicationStatusTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import blockTable from './tables/blockTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import claimTable from './tables/claimTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import gorpMigrationsTable from './tables/gorpMigrationsTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import inputTable from './tables/inputTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import jobStatusTable from './tables/jobStatusTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import outputTable from './tables/outputTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import supportTable from './tables/supportTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import transactionAddressTable from './tables/transactionAddressTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import transactionTable from './tables/transactionTable';
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
const {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
host,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
port,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
database,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
username,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
password,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
} = require('../../config/chainqueryConfig'); // TODO: Make '@config/siteConfig' work outside Webpack for testing/dev
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
if (!database || !username || !password) {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logger.warn('missing database, user, or password from chainqueryConfig');
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
}
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
// set sequelize options
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
const sequelize = new Sequelize(database, username, password, {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
host : host,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
import : port,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
dialect : 'mysql',
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
dialectOptions: {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
decimalNumbers: true,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
},
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logging: false,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
pool : {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
max : 5,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
min : 0,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
idle : 10000,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
acquire: 10000,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
},
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
operatorsAliases: false,
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
});
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
const db = {};
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.abnormal_claim = sequelize.import('abnormal_claim', abnormalClaimTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.application_status = sequelize.import('application_status', applicationStatusTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.address = sequelize.import('address', addressTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.block = sequelize.import('block', blockTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.claim = sequelize.import('claim', claimTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.gorp_migrations = sequelize.import('gorp_migrations', gorpMigrationsTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.input = sequelize.import('input', inputTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.job_status = sequelize.import('job_status', jobStatusTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.output = sequelize.import('output', outputTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.support = sequelize.import('support', supportTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.transaction_address = sequelize.import('transaction_address', transactionAddressTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db.transaction = sequelize.import('transaction', transactionTable.createModel);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
// run model.association for each model in the db object that has an association
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logger.info('associating chainquery db models...');
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
Object.keys(db).forEach(modelName => {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
if (db[modelName].associate) {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logger.info('Associating chainquery model:', modelName);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
db[modelName].associate(db);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
}
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
});
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
// establish mysql connection
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
sequelize
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
.authenticate()
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
.then(() => {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logger.info('Sequelize has established mysql connection for chainquery successfully.');
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
})
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
.catch(err => {
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
logger.error('Sequelize was unable to connect to the chainquery database:', err);
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
});
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.
export default db;
tiger5226 commented 2018-09-05 01:22:02 +02:00 (Migrated from github.com)
Review

this is only used for database migrations. Not of use to speech. I would ignore this table.

this is only used for database migrations. Not of use to speech. I would ignore this table.
tiger5226 commented 2018-09-05 01:22:43 +02:00 (Migrated from github.com)
Review

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.

This table is used for tracking background job statuses internal to chainquery. Most likely not useful for speech.
tiger5226 commented 2018-09-05 01:23:52 +02:00 (Migrated from github.com)
Review

same thing. this is an internal table of no importance to speech.

same thing. this is an internal table of no importance to speech.

View file

@ -0,0 +1,65 @@
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
const getterMethods = {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
// Add as needed, prefix all methods with `generated`
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
}
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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, {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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, BOOLEAN, INTEGER, TEXT, DECIMAL
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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(
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
'abnormal_claim',
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
{
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
id: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
primaryKey: true,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
name: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: STRING,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
claim_id: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: STRING,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
is_update: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
block_hash: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: STRING,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
transaction_hash: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: STRING,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
vout: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
output_id: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
value_as_hex: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: TEXT,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
value_as_json: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: TEXT,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
created_at: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
modified_at: {
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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: INTEGER,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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() { },
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
},
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
{
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
freezeTableName: true,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
getterMethods,
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
timestamps: false, // don't use default timestamps columns
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
}
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.
);
tiger5226 commented 2018-09-05 01:25:52 +02:00 (Migrated from github.com)
Review

These are timestamps, is it ok to create it as an integer?

These are timestamps, is it ok to create it as an integer?
skhameneh commented 2018-09-05 02:36:40 +02:00 (Migrated from github.com)
Review

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.

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.

View file

@ -0,0 +1,37 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'address',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
address: {
type: STRING,
set() { },
},
first_seen: {
type: INTEGER,
set() { },
},
created_at: {
type: INTEGER,
set() { },
},
modified_at: {
type: INTEGER,
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,33 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'application_status',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
app_version: {
type: INTEGER,
set() { },
},
data_version: {
type: INTEGER,
set() { },
},
api_version: {
type: INTEGER,
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,97 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'block',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
bits: {
type: STRING,
set() { },
},
chainwork: {
type: STRING,
set() { },
},
confirmations: {
type: STRING,
set() { },
},
difficulty: {
type: STRING,
set() { },
},
hash: {
type: STRING,
set() { },
},
height: {
type: STRING,
set() { },
},
merkle_root: {
type: STRING,
set() { },
},
name_claim_root: {
type: STRING,
set() { },
},
nonce: {
type: STRING,
set() { },
},
previous_block_hash: {
type: STRING,
set() { },
},
next_block_hash: {
type: STRING,
set() { },
},
block_size: {
type: STRING,
set() { },
},
block_time: {
type: STRING,
set() { },
},
version: {
type: STRING,
set() { },
},
version_hex: {
type: STRING,
set() { },
},
transaction_hashes: {
type: STRING,
set() { },
},
transactions_processed: {
type: STRING,
set() { },
},
created_at: {
type: INTEGER,
set() { },
},
modified_at: {
type: INTEGER,
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,177 @@
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
const logger = require('winston');
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
const {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
assetDefaults: { thumbnail: defaultThumbnail },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
details: { host }
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
} = require('../../../config/siteConfig'); // TODO: Change back to '@config/siteConfig' when done testing
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
const getterMethods = {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
generated_extension() {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
switch (this.content_type) {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
case 'image/jpeg':
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
case 'image/jpg':
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
return 'jpg';
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
case 'image/png':
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
return 'png';
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
case 'image/gif':
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
return 'gif';
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
case 'video/mp4':
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
return 'mp4';
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
default:
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
logger.debug('setting unknown file type as file extension jpg');
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:27:16 +02:00 (Migrated from github.com)
Review

Is jpg really a good default? Why not blank or unknown?

Is jpg really a good default? Why not blank or unknown?
tiger5226 commented 2018-09-05 01:28:09 +02:00 (Migrated from github.com)
Review

Also how do you handle nulls? A channel claim is not going to have any of the meta data fields. They will be null in the DB.

Also how do you handle nulls? A channel claim is not going to have any of the meta data fields. They will be null in the DB.
skhameneh commented 2018-09-05 02:33:43 +02:00 (Migrated from github.com)
Review

This is the same implementation as existing code in Spee.ch; it's implemented as a generated field.
I may need to revisit this for reusability.

This is the same implementation as existing code in Spee.ch; it's implemented as a generated field. I may need to revisit this for reusability.
return 'jpg';
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
}
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
// TODO: Factor this out.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
generated_thumbnail() {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
return this.thumbnail_url || defaultThumbnail;
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
generated_channel() {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
console.log(this);
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
//
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
}
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
}
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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, {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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, BOOLEAN, INTEGER, TEXT, DECIMAL
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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(
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
'claim',
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
{
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
id: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
primaryKey: true,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
transaction_hash_id: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
vout: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
name: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
claim_id: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
claim_type: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
publisher_id: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
publisher_sig: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
certificate: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
sd_hash: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
transaction_time: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
version: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
value_as_hex: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
value_as_json: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
valid_at_height: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
height: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
effective_amount: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
author: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
description: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
content_type: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
is_nsfw: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
language: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
thumbnail_url: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
title: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
fee: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: DECIMAL(58, 8),
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
fee_currency: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
is_filtered: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
tiger5226 commented 2018-10-09 02:11:05 +02:00 (Migrated from github.com)
Review

This is an old column. I need to delete this. Not sure why it is in the schema. I will create an issue for it.

This is an old column. I need to delete this. Not sure why it is in the schema. I will create an issue for it.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
bid_state: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
created_at: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
modified_at: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: INTEGER,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
fee_address: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
claim_address: {
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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: STRING,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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() { },
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
},
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
{
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
freezeTableName: true,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
getterMethods,
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
timestamps: false, // don't use default timestamps columns
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
}
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.
);
tiger5226 commented 2018-09-05 01:28:59 +02:00 (Migrated from github.com)
Review

This is a boolean that is a TINYINT(1) in the database.

This is a boolean that is a `TINYINT(1)` in the database.
tiger5226 commented 2018-09-05 01:29:58 +02:00 (Migrated from github.com)
Review

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 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.

View file

@ -0,0 +1,25 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'gorp_migrations',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
applied_at: {
type: INTEGER,
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,77 @@
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
const getterMethods = {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
// Add as needed, prefix all methods with `generated`
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
}
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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, {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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, INTEGER, TEXT, DECIMAL
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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(
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
'input',
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
{
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
id: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
primaryKey: true,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
transaction_id: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
transaction_hash: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: STRING,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
input_address_id: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
is_coinbase: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
coinbase: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: STRING,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
prevout_hash: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: STRING,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
prevout_n: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
prevout_spend_updated: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
sequence: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
value: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: DECIMAL(18, 8),
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
script_sig_asm: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: TEXT,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
script_sig_hex: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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: TEXT,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
created: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
modified: {
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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() { },
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
},
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
{
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
freezeTableName: true,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
getterMethods,
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
timestamps: false, // don't use default timestamps columns
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
}
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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
);
tiger5226 commented 2018-09-05 01:30:22 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:30:46 +02:00 (Migrated from github.com)
Review

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?
skhameneh commented 2018-09-05 02:42:19 +02:00 (Migrated from github.com)
Review

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

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

View file

@ -0,0 +1,33 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'job_status',
{
job_name: {
primaryKey: true,
type: STRING,
set() { },
},
last_sync: {
type: INTEGER,
set() { },
},
is_success: {
type: INTEGER,
set() { },
},
error_message: {
type: TEXT,
set() { },
}
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,77 @@
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
const getterMethods = {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
// Add as needed, prefix all methods with `generated`
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
}
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
export default (sequelize, {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
}) => sequelize.define(
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
'output',
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
{
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
id: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
primaryKey: true,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
transaction_id: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
transaction_hash: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: STRING,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
value: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: DECIMAL(18, 8),
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
vout: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: STRING,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
script_pub_key_asm: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: TEXT,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
script_pub_key_hex: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: TEXT,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
required_signatures: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
address_list: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: TEXT,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
is_spent: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
tiger5226 commented 2018-09-05 01:33:13 +02:00 (Migrated from github.com)
Review

This is a JSON array. Not sure if you can specify that here or not.

This is a JSON array. Not sure if you can specify that here or not.
skhameneh commented 2018-10-09 20:13:32 +02:00 (Migrated from github.com)
Review

Can't, not supported unless using a virtual field. I might add a custom getter method.

Can't, not supported unless using a virtual field. I might add a custom getter method.
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
spent_by_input_id: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
created_at: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
modified_at: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: INTEGER,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
claim_id: {
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
type: STRING,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
set() { },
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
}
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
},
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
{
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
freezeTableName: true,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
getterMethods,
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
timestamps: false, // don't use default timestamps columns
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
}
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean
);
tiger5226 commented 2018-09-05 01:33:23 +02:00 (Migrated from github.com)
Review

boolean

boolean

View file

@ -0,0 +1,49 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'support',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
supported_claim_id: {
type: STRING,
set() { },
},
support_amount: {
type: DECIMAL(18, 8),
set() { },
},
bid_state: {
type: STRING,
set() { },
},
transaction_hash_id: {
type: STRING,
set() { },
},
vout: {
type: INTEGER,
set() { },
},
created_at: {
type: INTEGER,
set() { },
},
modified_at: {
type: INTEGER,
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,34 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'transaction_address',
{
transaction_id: {
primaryKey: true,
type: INTEGER,
set() { },
},
addess_id: {
primaryKey: true,
type: INTEGER,
set() { },
},
debit_amount: {
type: DECIMAL(18, 8),
set() { },
},
credit_amount: {
type: DECIMAL(18, 8),
set() { },
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,73 @@
const getterMethods = {
// Add as needed, prefix all methods with `generated`
}
export default (sequelize, {
STRING, BOOLEAN, INTEGER, TEXT, DECIMAL
}) => sequelize.define(
'transaction',
{
id: {
primaryKey: true,
type: INTEGER,
set() { },
},
block_hash_id: {
type: STRING,
set() { },
},
input_count: {
type: INTEGER,
set() { },
},
output_count: {
type: INTEGER,
set() { },
},
fee: {
type: DECIMAL(18, 8),
set() { },
},
transaction_time: {
type: INTEGER,
set() { },
},
transaction_size: {
type: INTEGER,
set() { },
},
hash: {
type: STRING,
set() { },
},
version: {
type: INTEGER,
set() { },
},
lock_time: {
type: INTEGER,
set() { },
},
raw: {
type: TEXT,
set() { },
},
created_at: {
type: INTEGER,
set() { },
},
modified_at: {
type: INTEGER,
set() { },
},
created_time: {
type: INTEGER,
set() {},
},
},
{
freezeTableName: true,
getterMethods,
timestamps: false, // don't use default timestamps columns
}
);

View file

@ -0,0 +1,11 @@
import AbnormalClaimModel from '../models/AbnormalClaimModel';
export default {
createModel(...args) {
return AbnormalClaimModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import AddressModel from '../models/AddressModel';
export default {
createModel(...args) {
return AddressModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import ApplicationStatusModel from '../models/ApplicationStatusModel';
export default {
createModel(...args) {
return ApplicationStatusModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import BlockModel from '../models/BlockModel';
export default {
createModel(...args) {
return BlockModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import ClaimModel from '../models/ClaimModel';
export default {
createModel(...args) {
return ClaimModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import GorpMigrationsModel from '../models/GorpMigrationsModel';
export default {
createModel(...args) {
return GorpMigrationsModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import InputModel from '../models/InputModel';
export default {
createModel(...args) {
return InputModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import JobStatusModel from '../models/JobStatusModel';
export default {
createModel(...args) {
return JobStatusModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import OutputModel from '../models/OutputModel';
export default {
createModel(...args) {
return OutputModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import SupportModel from '../models/SupportModel';
export default {
createModel(...args) {
return SupportModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import TransactionAddressModel from '../models/TransactionAddressModel';
export default {
createModel(...args) {
return TransactionAddressModel(...args);
},
associate(db) {
// associate
}
}

View file

@ -0,0 +1,11 @@
import TransactionModel from '../models/TransactionModel';
export default {
createModel(...args) {
return TransactionModel(...args);
},
associate(db) {
// associate
}
}