[AAA-38] Incorrect database initialization Created: 19/Jun/15 Updated: 21/Mar/19 Resolved: 24/Jun/15 |
|
| Status: | Resolved |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anton Ivanov | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3820 |
| Description |
|
H2 database initialization parameters were left "as is" verbatim from sqlite3 which is 1. Incorrect Background: It was possible to recover, reset or otherwise "fix" the database in Helium using a range of tools - command line sqlite3 utility, python, perl, etc. That functionality should be possible with the H2 database as well due to H2 providing reasonable level of support for the Postgresql connection protocol. Unfortunately, it is not possible to use it because the specific H2 postgresql protocol implementation insists on valid username and password. As a result it is no longer possible to recover, reset, backup cleanly in non-binary form for upgrade and migration purposes the database. Solution - add username and password to database instantiation (unfortunately not backwards compatible as the current Li database is not created correctly). |
| Comments |
| Comment by Wojciech Dec [ 24/Jun/15 ] |