Finished Database working #12
Conversation
Those methods do not correspond entry ones
Entry file needs new coverage and analysis
Moved some methods to parent class as they are working the same way for all subclasses
"cidCategory" is not necessary to be in Entry child classes/tables, so it was removed
…r" for obtaining a new SQL script and included new method at IOManager for reading OSQL files
|
CodeFactor found an issue: Duplicate Code It's currently on: It uses |
|
CodeFactor found an issue: Duplicate Code It's currently on: This code is required to be overridden by |
|
CodeFactor found an issue: Duplicate Code It's currently on: Methods declared by interfaces, and there is no need of using abstract class- can be safely ignored |
|
CodeFactor found an issue: Duplicate Code It's currently on: Method declared by interface, this error can be safely ignored |
|
CodeFactor found an issue: Duplicate Code It's currently on: Uses |
…into database # Conflicts: # APP/.idea/caches/build_file_checksums.ser # APP/app/build.gradle # APP/app/src/main/java/javinator9889/securepass/io/database/DatabaseManager.java # APP/app/src/main/java/javinator9889/securepass/io/database/operations/CommonOperations.java
Minor corrections on "CommonOperations" class (the executor now finishes also when "finishConnection()" is called) and also inside "CategoryOperations" class. The new method allows the ability to remove the ID field inside the "Enum" classes (in a future, enumerations will be replaced with "StringDef" - see: https://android.jlelse.eu/android-performance-avoid-using-enum-on-android-326be0794dc3) Finally, lots of conflict files were removed as they are not essential
…s not correspond always to the table ones)
In SQLite, if there is any FOREIGN KEY, it will not be necessarily a PRIMARY KEY, as it can violate constraints (NOT NULL) and at some cases there will be NULL primary keys and multiple (NON UNIQUE) FOREIGN KEYS marked as PRIMARY KEYS
Able to merge - tests needed