Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
hydws
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
sarsonl
hydws
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
bbc960dcc253c5c1b8ad11c36f9f7c3753a213f4
Select Git revision
Branches
4
develop
default
feat/extend_query_params
master
working_progress
4 results
Begin with the selected commit
Created with Raphaël 2.2.0
25
Jun
24
21
7
May
6
5
3
2
30
Apr
29
24
18
Real values held in real value table
working_progress
working_progress
LiteratureSource relationships -> one to one
develop
develop
Altering relationships in LiteratureSource classes uselist=False
PEP8 of file
Fixing of unit tests and addition to READMS.md
Change to Literature Source & Creation Info
Change datetime serialization so no timezone.
Addition of logic so that parents always returned if no children
Do not return sections if epoch time not valid
Route which returns specific borehole defined to return JSON object
Addition Flask-Migrate
Minor updates to docstrings, addition of test SQLite db
Addition of unit tests and refactoring code
Reimplementation of schema logic and parsing data
Change attr names to match with 'm_'+column key
Moving query filter class to its own file
Column attributes now use no m_ prefix
Start of full implementation of HYDWS after handover damb->sarsonl
Add filter query class to centralize column filtering.
Refactoring code to try and minimise use of same code multiple times. Have to discuss the use of None filtering in query as I am not sure about the purpose.
Refactoring code to try and minimise use of same code multiple times. Have to discuss the use of None filtering in query as I am not sure about the purpose.
feat/extend_que…
feat/extend_query_params
Return ordered result
Join with HydraulicSample
[DOC]: Add note
Correct column type (QuakeML Quantity)
Fix typo
[DOC]: Add docstrings
Add time constraints filter parameters
Skip fields with empty values
Implement first resource
Define GeneralSchema
Correct argument list
Add JSON mimetype
[STY]: Correct PEP8
[MAINT]: Rename fields
Remove SQLite file only without --sql
[MAINT]: Provide utility to init (and create) DB
[MAINT]: Provide package for output streams
Add initial tox.ini
[MAINT]: Move DB related facilities to db package
Loading