File:RDB connection.ANA: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
31.7.2008 Jouni Tuomisto | 31.7.2008 Jouni Tuomisto | ||
Identified problems: | Identified problems: | ||
* Inp_loc_of_result can calculate at least 800000 rows, but Write_locres is unable to write that data into the database. | * Inp_loc_of_result can calculate at least 800000 rows, but Write_locres is unable to write that data into the database. Maybe the problem is in the MySQL side, see [http://www.pyrkilo.fi/phpmyadmin/Documentation.html#faq1_16]. | ||
* Inp_run_list does not work with composite traffic model cost variables. I attempted to write the following variables (from Var_fo_rdb node): | * Inp_run_list does not work with composite traffic model cost variables. I attempted to write the following variables (from Var_fo_rdb node): | ||
Revision as of 06:08, 1 August 2008
Connection module for writing variable results into the Result database. Created by --Jouni 14:59, 18 July 2008 (EEST).
31.7.2008 Jouni Tuomisto Identified problems:
- Inp_loc_of_result can calculate at least 800000 rows, but Write_locres is unable to write that data into the database. Maybe the problem is in the MySQL side, see [1].
- Inp_run_list does not work with composite traffic model cost variables. I attempted to write the following variables (from Var_fo_rdb node):
'Fig_3_cost_by_source' 9 1 'Fig_5a_societal_costs' 10 1 'Fig_5b_subsidies' 11 0 'Fig_5c_expanding' 12 1
but this resulted in an error message from Cap_variab_2: "first parameter in sortindex must be a table". This error does not occur when the node is calculated, only when I attempt to write it into the database. See an email to Dale Rice 31.7.2008.
File history
Click on a date/time to view the file as it appeared at that time.
| Date/Time | Dimensions | User | Comment | |
|---|---|---|---|---|
| current | 09:48, 9 October 2008 | (55 KB) | Jouni (talk | contribs) | Added new functionality for describing locations. This is already reflected in the structure of the RDB. There is a development need in New_locs. |
| 08:17, 16 September 2008 | (53 KB) | Jouni (talk | contribs) | ALL so far identified problems solved. This version is compatible with the new, lighter Result Database structure. | |
| 13:43, 15 September 2008 | (55 KB) | Jouni (talk | contribs) | Some technical improvements. But the Missing item indices are actually really tricky, no breakthrough yet. | |
| 14:14, 8 September 2008 | (55 KB) | Jouni (talk | contribs) | Now the model checks for existing locations and uses them correctly in creating new indices. | |
| 14:36, 5 September 2008 | (55 KB) | Jouni (talk | contribs) | Locations must be text values! Now corrected. | |
| 10:58, 3 September 2008 | (52 KB) | Jouni (talk | contribs) | Problem was that database update corrupted the numbering of tables. Now it is corrected. This simplified the model. | |
| 14:03, 2 September 2008 | (52 KB) | Jouni (talk | contribs) | Now it works! Although there is something strange going on with Inp_loc_of_result when Testvariables are used. | |
| 13:16, 1 September 2008 | (52 KB) | Jouni (talk | contribs) | Almost works with online writing. | |
| 17:17, 30 August 2008 | (49 KB) | Jouni (talk | contribs) | Old code removed. Input form outline updated. The module still have dummies for offline work; these must be removed for real use. | |
| 17:02, 30 August 2008 | (68 KB) | Jouni (talk | contribs) | Completely new operationalisation. Now the idea is that the edit tables only show the information that is needed. What is needed is checked from the RDB online. The used needs not know object id numbers. |
You cannot overwrite this file.
File usage
There are no pages that use this file.