summaryrefslogtreecommitdiff
path: root/queries
Commit message (Collapse)AuthorAgeFilesLines
* rewrite in NodeJSschneefux2017-03-284-109/+0
|
* Fix https://github.com/vainglorygame/meta/issues/44.Kapil Viren Ahuja2017-03-151-1/+1
| | | | We will need a query to update this in production - I doubt we can fix older data as we don’t have anything from Raw…
* player: insert skill_tierschneefux2017-03-121-1/+2
|
* hotfix API returning xp as floatVainsocial root2017-03-121-1/+1
|
* cache statements, smart spider, refactor upsertsschneefux2017-03-081-1/+1
|
* enable shardid and fix timestampschneefux2017-03-051-2/+6
|
* add created_at to participantschneefux2017-03-051-0/+3
|
* Fixed the last match cols which was sending this job into a hung state ↵Kapil Viren Ahuja2017-03-041-1/+1
| | | | without throwing any exception.
* Col case changesKapil Viren Ahuja2017-03-044-37/+37
|
* Fixes col type as per defect in VainsocialKapil Viren Ahuja2017-03-031-1/+1
|
* process turretKillsschneefux2017-03-021-0/+1
|
* reference from participant to rosterschneefux2017-02-271-0/+2
|
* process roster's match_apiIdschneefux2017-02-271-1/+3
|
* rewrite to use joblib (fixes #20), use updated raw schema, check for duplicatesschneefux2017-02-264-60/+81
|
* update queries to work with vainsocial.com#developschneefux2017-02-202-4/+4
|
* process partitions concurrentlyschneefux2017-02-204-4/+4
|
* change to how the FK are managed in EORMkvahuja2017-02-191-1/+1
|
* match to roster relationshipkvahuja2017-02-191-1/+4
|
* refactoring as part of https://github.com/vainglorygame/vainsocial.com/issues/17kvahuja2017-02-183-46/+28
|
* match and roster tables refactoredkvahuja2017-02-172-12/+23
|
* refactored to adapt to changes in Web's DB model.Kapil Viren Ahuja2017-02-171-10/+4
| | | | | this will only work with branch - https://github.com/vainglorygame/vainsocial.com/tree/features/db-model-refactoring
* workaround for participants not including some dataschneefux2017-02-161-9/+9
|
* 1. using the right table names in SQL. 2. also put in some exception ↵Kapil Viren Ahuja2017-02-164-5/+6
| | | | | | | | handling which spits out the error and moves on instead of exiting (#11) * 1. using the right table names in SQL. 2. also put in some exception handling which spits out the error and moves on instead of exiting * ID in participant table is participant ID. we need a mapping for player ID in Web to get a player's matches.
* load processor queries from sql filesschneefux2017-02-154-0/+84