ra:development
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ra:development [2018/10/19 15:06] koubel [Database] |
ra:development [2021/12/11 18:13] (current) koubel [UI test] |
||
|---|---|---|---|
| Line 51: | Line 51: | ||
| Some customers has very special database setup, see Customers paragraph. | Some customers has very special database setup, see Customers paragraph. | ||
| - | Online Data | + | OnlineData, OnlineDataProcessed |
| + | |||
| + | OnlineData and OnlineDataProcessed are special tables for data processing. Important column is ROM. It defines observed "unit" which can send online data - table dbUnit. | ||
| + | |||
| + | Showing online data processed for particular vehicle - ROM. | ||
| + | |||
| + | select * from OnlineDataProcessed | ||
| + | where ROM = '352094087747884' and date > '2018-10-01' and date < '2018-10-10' | ||
| + | |||
| + | It's necessary to specify minimal date interval, because table is huge and queries can timeout. | ||
| + | |||
| + | Important table, columns: | ||
| + | |||
| + | * OnlineDataProcessed.ID_ONLINE_DATA_ERROR_TYPE must be not NULL | ||
| + | * OnlineDataProcessed.ID_VEHICLE must be filled. If ins't filled, it means that vehicle was imported later then first online data was arrived. | ||
| + | * DbUnit - it's table for ROMs, it defines which OnlineDataSource is used for particular ROM. | ||
| + | * VehicleUnit - relation table between unit and vehicle. | ||
| + | |||
| + | Copying data from one onlinedata database to another, see more information on [[http://10.0.2.27/doku.php?id=protank_dynamics:pd_databaze#kopirovani_online_dat|raltra wiki]] | ||
| There is special fetching process in code. Sometimes it's necessary to add columns into online data database from the OnlineDataColumns table, it's processed via stored procedures | There is special fetching process in code. Sometimes it's necessary to add columns into online data database from the OnlineDataColumns table, it's processed via stored procedures | ||
| Line 66: | Line 85: | ||
| * defects - závady | * defects - závady | ||
| - | OnlineData, OnlineDataProcessed | ||
| - | |||
| - | db.Unit - information about ROM - ROM is paired with Vehicle -> VehicleUnit table | ||
| - | select * from OnlineDataProcessed | ||
| - | where ROM = '352094087747884' and date > '2018-10-01' and date < '2018-10-10' | ||
| - | If ID_ONLINE_DATA_ERROR_TYPE must be not NULL, ID_VEHICLE must be filled. If ins't filled, it means that vehicle was imported later then first online data was arrived. | ||
| ====== Customers ====== | ====== Customers ====== | ||
| Line 154: | Line 167: | ||
| These are test for LogBook which opens page properly. | These are test for LogBook which opens page properly. | ||
| But there can be problem with deployed master - it triggers the test automatically. | But there can be problem with deployed master - it triggers the test automatically. | ||
| + | |||
| + | ====== Development notices ====== | ||
| + | |||
| + | Jo a co jsi tam psal s tím že jsem na Tahiti a vyplňování stazky. To jsem opravdu kokot, protože vyplňuju svoz nějaké popelnici co je v Praze z počítače na Tahati, takže je jasné že bude problém. | ||
| + | |||
| + | Browsery vždycky zobrazují lokální čas podle nastavení celého počítače a jakmile by se do tohohle nativního chování začalo hrabat, tak je zaděláno na obrovské problémy naprosto všude kde pracuje v browseru s datumem a to bychom si tedy už fakt zavařili. Prostě si změním timezone v počítači na Prahu. | ||
| + | |||
| + | To už tedy posílat tu timezone klienta a ať si ty timeshifty dělá server při odesílání a ukládání dat a klienti pak uvidí to, co se děje někde v timezone dané někde nějakým nastavením na backendu pro zákazníka. Ale určitě neřešit na klientovi. | ||
| + | |||
| + | Ono do důsledku se klidně může lišit timezone jednotlivých lokalit jednoho zákazníka, nebo dokonce jednotlivých fyzických objektů - míst svozů, nádob, tras atd atd., např. v tom Maďarsku, Polsku atd atd. Takže každý "fyzický objekt" by měl mít i někde v db nastavenu timezone ale řešit by to měl server na základě timezone, co dostane od klienta. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | |||
ra/development.1539954373.txt.gz · Last modified: 2018/10/19 15:06 by koubel
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
