| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Prior to this commit the overlay would not set the owner info if the
contact attribute was found, breaking backwards compatibility. To allow
for this backwards compatibility while maintaining multiple owner
support layman will be defaulting to the "contact" attribute if it is
present in any XML overlays.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The api function get_all_info() is being deprecated as it was much
slower than the get_info_str() function and was no longer used in
layman's code. The only instance found making use of it was older test
code which has been changed to also use the get_info_str() function.
external.py: Deprecates the get_all_info() function and adds multiple
owner testing compatibility.
api.py: Removes the get_all_info() function.
cli.py: Removes commented out use of get_all_info() function.
global-overlays.json: Changes structure of 'owner' attribute to reflect
changes for multiple owner support.
|
|
|
|
|
|
| |
The previous method still made use of owner_name and owner_email to see
if the two were equal while it should've been checking for the "owners"
overlay attribute.
|
|
|
|
|
|
| |
These modifications remove a lot of duplicated prompts that were created
when trying to prompt the user for an item that could be of more than
one value.
|
| |
|
|
|
|
|
|
| |
As this function exists with the API consumer in mind the function
was well overdue for getting it the result keys updated to reflect
all the ongoing changes in layman's API.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This parameter has been added in order to obtain proper
parallelization support for layman sqlite databases. With this
additional parameter it prompts the sqlite db module's write function to
simply return when removing an overlay, preventing it from re-adding any
database entires and causing oddness, run-time errors, or other unwanted
badness.
|
|
|
|
|
|
| |
Due to the fact that including the owner name isn't necessary layman
needed to modify the way it gathered owner information to prevent
run-time errors.
|
| |
|
|
|
|
|
|
| |
sqlite_db.py: Also changes the way in which feeds are gathered in
read_db(), this shows the nature of feeds being an unrequired attribute
of the overlay.
|
| |
|
| |
|
|
|
|
|
|
| |
constants.py: Adds sqlite to list of supported database modules.
setup.py: Adds db_modules.sqlite_db.sqlite_db to list of installable
modules.
|
| |
|
| |
|
|
|
|
| |
updater.py: Adds proper line spacing for database migration output
|
|
|
|
|
|
|
|
|
| |
In order to preserve the config file set up of the layman config
file the set_db_type() function has been modified to not use
configparser as it doesn't preserve comments. Changes have also
been made in case the database file ends with the old extension,
so the backup name will end in ".bak" as opposed to the database's
file type.
|
| |
|
| |
|
|
|
|
|
|
|
| |
To avoid namespace collisions in py2.7 the database modules needed
to have "_db" appended to their name. In order to avoid having this
ugliness in the user's config file and elsewhere in layman's code
the DbBase class simply adds the "_db" portion of the name itself.
|
| |
|
|
|
|
|
| |
As the next release will include some noticeable changes an increment
of the second version number in layman was necessary.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The Overlay, DbBase, and DB would require the db_type config option
to be set. To prevent it from falling back on config option defaults
it's best to specify it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If the Overlay object has no name then trying to use the name would
result in erroneous or illogical reporting.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also reorganizes functions alphabetically.
|
|
|
|
|
|
|
|
|
|
|
| |
overlay.py: Modifies what from_dict() expects in the overlay dictionary
constants.py: Modifies POSSIBLE_COMPONENTS and REQUIRED_COMPONENTS to
reflect change in overlay.py
maker.py: Modifies components that form the overlay dict to follow in
suit of what from_dict() expects.
These changes have been made primarily for uniformity with the
from_xml() function.
|
|
|
|
|
|
| |
These functions are in the DbBase class and will continue to be used
in that class. As such there's no need for any DBHandler class to
include them in their code.
|
|
|
|
|
|
|
| |
Logically speaking, if the database "document" text is provided then
it will likely not be universal to every database provided. Therefore
adding another parameter that specifies the type of text that is being
provided will help distinguish which database type it is.
|
| |
|
|
|
|
| |
This prevents namespace collisions with the required xml class.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This was done to allow for only one read*() function and add
compatibility with the way read() was originally set up.
xml.py: read_db() is also modified in this file for the same purpose.
remotedb.py: changes the calling of self.read() to self.read_db().
|
|
|
|
|
|
| |
Other changes include code clean up and the disabling of the add_new()
function. Currently the DbBase only supports the XML DBHandler but
more support will be added soon.
|
| |
|