Home
About
Blog
Products
Forum
Support
Contact
Sunbelt Computer Software
PL/B Language Development and Support
Home
About
Blog
Products
Forum
Support
Contact
pmacct/sql/README.timestamp at master · pmacct/pmacct · GitHub
Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
See all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
pmacct
pmacct
Repository navigation
Code
Issues
31
(31)
Pull requests
18
(18)
Actions
Projects
Wiki
Security and quality
Insights
More
items
Files
Expand file tree
master
Breadcrumbs
pmacct
/
sql
/
README.timestamp
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
47 lines (40 loc) · 2.47 KB
master
Breadcrumbs
pmacct
/
sql
/
README.timestamp
Copy path
Top
File metadata and controls
Code
Blame
47 lines (40 loc) · 2.47 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
This document doesn't replace documentation relevant to the database software you are
using, ie. README.mysql, README.pgsql or README.sqlite3.
The 'timestamp_start', 'timestamp_end', 'timestamp_arrival', 'timestamp_min' and
'timestamp_max' fields.
'timestamp_start' and 'timestamp_end' fields are being introduced to support logging
of traffic and events via pmacct (mainly NetFlow/IPFIX feature). 'timestamp_arrival'
records libpcap packet timestamp and sFlow/NetFlow/IPFIX packet arrival time at the
collector; 'timestamp_min' and 'timestamp_max' fields support stitching of flows (or
samples if sfacctd or packets if pmacctd), for more info see nfacctd_stitching feature
in CONFIG-KEYS.
Timestamps resolution is up to the msec level and for this reason time residual fields
are optionally introduced ie. 'timestamp_start_residual', 'timestamp_end_residual':
this is because support for resolutions beyond the secs level is something not popular
among the supported RDBMS, ie. only recent versions of MySQL >= 5.6.4 appear to support
it, hence the choice to go for two separate fields. Timestamp resolution can be cut
to secs level by setting timestamps_secs config directive to 'true': in this case the
residual fields can be omitted in the table schema. The guidelines below (typically
n MySQL format) are to add all the described primitives to the SQL schema:
* timestamp_start and timestamp_start_residual fields:
- To declare the fields:
- "timestamp_start DATETIME NOT NULL,"
- "timestamp_start_residual INT UNSIGNED NOT NULL,"
- To add them to the primary key:
- "PRIMARY KEY (..., timestamp_start, timestamp_start_residual, ...)"
* timestamp_end and timestamp_end_residual fields:
- To declare the fields:
- "timestamp_end DATETIME NOT NULL,"
- "timestamp_end_residual INT UNSIGNED NOT NULL,"
- To add them to the primary key:
- "PRIMARY KEY (..., timestamp_end, timestamp_end_residual, ...)"
* timestamp_arrival and timestamp_arrival_residual fields:
- To declare the fields:
- "timestamp_arrival DATETIME NOT NULL,"
- "timestamp_arrival_residual INT UNSIGNED NOT NULL,"
- To add them to the primary key:
- "PRIMARY KEY (..., timestamp_arrival, timestamp_arrival_residual, ...)"
This works similarly for 'timestamp_min', 'timestamp_min_residual', 'timestamp_max'
and 'timestamp_max_residual'.
The primitive is not declared as part of any default table version; yet will not fail
version checks which are enabled when 'sql_optimize_clauses' feature is disabled.
You can’t perform that action at this time.