Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updatating the DNS examples to non tracking #122

Closed
wants to merge 12 commits into from
Closed

Updatating the DNS examples to non tracking #122

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
67c329e
Updatating the DNS examples to non tracking
spirillen Sep 20, 2020
525dfee
(DRAFT) Information about SQL tables
spirillen Sep 20, 2020
1aa1b75
Switched to y own profile
spirillen Sep 20, 2020
7aef5c7
Switching profile url for @spirillen
spirillen Sep 20, 2020
8a953f2
Added new projects
spirillen Sep 20, 2020
3c6f5d2
Describing the urllib3 errors
spirillen Sep 20, 2020
f1338d9
A few enhangement according to comments
spirillen Sep 24, 2020
7c16e21
Removed urllib3 as fixed
spirillen Sep 24, 2020
0c75af5
Merge pull request #9 from spirillen/spirillen-contributors-uri
spirillen Sep 24, 2020
4d37e11
Added subtitile (draft) of SQL layout
spirillen Sep 24, 2020
e237226
Added the Focal Fossa test environment
spirillen Oct 6, 2020
3bd95cc
changed python 3.7.8 to 3.8.2 as default (20.04)
spirillen Oct 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Prev Previous commit
Next Next commit
Added subtitile (draft) of SQL layout 
I've Added the second level title of `SQL Layout` to draft.

This is done for the time of developing the SQL as I'll foresees several changes in the near future.
  • Loading branch information
@spirillen
spirillen committed Sep 24, 2020
commit 4d37e116f807373ea849c6e8f6e290ab230a234f
13 changes: 8 additions & 5 deletions docs/components/databases.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,9 @@ How to use the :code:`mariadb` or :code:`mysql` format?
SQL Layout:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As of a possible merge of https://github.com/funilrys/PyFunceble/tree/issue-118 in the coming days, All INT (except for http_status_code) will be converted to BIGINT.

Copy link
Contributor Author

@spirillen spirillen Sep 24, 2020 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take note of that. Why I've left it with a "open" wildcard (*INT???), as you notice they are followed by a note that I would have expected a BOOL in those cases.

What about my question marks in the SQL Layout: L118-L177 ?

Another thing I just noticed, it the lines L73-L108 even relevant anymore after changing to sqlachemy?

^^^^^^^^^^^

**DRAFT**:
^^^^^^^^^^

The layout and data within the Sql database and how they are used should
currently be following this patterns.

Expand All @@ -127,26 +130,26 @@ alembic_version
pyfunceble_file
- :code:`id` Primary key, auto_increment
- :code:`created` creation date of the record
- :code:`modified` Data the record was last tested, altered
- :code:`modified` Date the record was last tested, (altered)
- :code:`path` source of the file tested. URI or File_path
- :code:`test_completed` (bool) this data is used for picking up a
interrupted (broken) test or in CI for auto-continue :code:`-c`

pyfunceble_mined
- :code:`id` Primary key, auto_increment
- :code:`created` creation date of the record
- :code:`modified` Data the record was last tested, altered
- :code:`modified` Date the record was last tested, altered
- :code:`subject_id` key_ref to :code:`pyfunceble_status.id`
- :code:`file_id` key_ref to :code:`pyfunceble_file.id`
- :code:`mined` the full fqdns results of a :code:`--mining` response

pyfunceble_status
- :code:`id` Primary key, auto_increment
- :code:`created` creation date of the record
- :code:`modified` Data the record was last tested, altered
- :code:`modified` Date the record was last tested, altered
- :code:`file_id` (one to many relation) to :code:`pyfunceble_file.id`
This is used to extract where a record comes from.
- :code:`tested` IS the actual record tested in full (domain/URI)
This is used to extracting where a record comes from.
- :code:`tested` Is the actual record tested in full (domain/URI)
- :code:`_status` ACTIVE/INACTIVE status from the PyFunceble test (Twice??)
- :code:`status` ACTIVE/INACTIVE status from the PyFunceble test (Twice??)
- :code:`_status_source` The technique to determine the status WHOIS/DNSLOOKUP (Twice??)
Expand Down