ping-dataexport 0.2.0__tar.gz → 0.2.2__tar.gz

{ping_dataexport-0.2.0/src/ping_dataexport.egg-info → ping_dataexport-0.2.2}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: ping-dataexport
-Version: 0.2.0
-Summary: Universal database data export to CSV/TXT/Parquet — streaming, typed, no pandas
+Version: 0.2.2
+Summary: PING's Data Export Tool - To Parquet/CSV/TEXT as Accelerator for Data & AI Project
 Author: vorapol
 License-Expression: Apache-2.0
 Keywords: export,database,csv,parquet,etl,data-platform,airflow
@@ -31,6 +31,9 @@ Dynamic: license-file
 
 ## PING (ping-godhand)'s Universal Data Exporter
 
+> **Provided as-is. No support, no warranty, no roadmap commitments, use at
+> your own risk.**
+
 ## คำอธิบาย (ภาษาไทย)
 
 โปรแกรมช่วย Export ข้อมูลอย่างง่าย: เชื่อมต่อฐานข้อมูล รันคำสั่ง SQL
@@ -178,14 +181,14 @@ All options:
 | `-m` | `--mode` | export mode: `groupby` \| `date` \| `relativedate` \| `monthbydate` \| `splitrow` \| `watermark` — see section 4 |
 | `-col` | `--column` | column the mode partitions on |
 | `-row` | `--row` | rows per file (`-m splitrow`) |
-| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd` |
+| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd`; omitted with `-dr`/`-mr` ⇒ today (system date) |
 | `-dt` | `--dateto` | end date `yyyy-MM-dd` (`-m date`) |
 | `-dr` | `--daysrelative` | days back from `-df` (`-m relativedate`) |
 | `-mr` | `--monthsrelative` | months back from `-df` (`-m monthbydate`) |
 | `-rm` | `--removeexisting` | `Yes`: clear the output directory before exporting |
 | `-j` | `--job` | run one job.ini section — see section 5 |
 | `-jf` | `--jobfile` | job file path (default `./job.ini`) |
-| `-pl` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count) |
+| `-p` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count); `-pl` still works as a legacy alias |
 | `-n` | `--name` | job name shown in logs and the default log filename |
 | `-cf` | `--configfile` | config file path (default `./config.ini`) |
 | `-lf` | `--logfile` | log file path |
@@ -225,7 +228,8 @@ daily/
 └── sales_2026-01-05.csv
 ```
 
-**`relativedate` — N days back from an anchor date, anchor included:**
+**`relativedate` — N days back from an anchor date, anchor included
+(omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m relativedate -col txn_date \
@@ -240,7 +244,7 @@ rel/
 ```
 
 **`monthbydate` — N months back plus the anchor month (the anchor month stops
-at the anchor date):**
+at the anchor date; omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m monthbydate -col txn_date \
@@ -295,7 +299,7 @@ file — see *Output and logs* below):
 
 Put recurring exports in a job file so you never retype long commands. Each
 `[Section]` is **one job**: run one with `-j SectionName`, or all of them at
-once with `-pl`. Every key is simply a CLI option written as a config key:
+once with `-p`. Every key is simply a CLI option written as a config key:
 
 ```ini
 [DailySales]
@@ -319,7 +323,7 @@ Output=out/full_dump.parquet
 ```bash
 ping-dataexport -j DailySales                 # one section (job.ini by default, -jf elsewhere)
 ping-dataexport -j DailySales -od other_dir   # CLI options override the section
-ping-dataexport -pl 4                         # ALL sections in parallel, 4 workers
+ping-dataexport -p 4                          # ALL sections in parallel, 4 workers
 ```
 
 Every job.ini key and the CLI option it mirrors (keys are case-insensitive):
@@ -381,7 +385,7 @@ only, no metadata lookups.
 - Every run logs structured lines to stdout and to a log file:
   `-lf path` > `LogFile=` in config.ini > default
   `{ExportFolder}/logs/log_{jobname}.txt`.
-- CLI exit codes: `0` success, `1` failure (in `-pl` parallel mode: `1` if any
+- CLI exit codes: `0` success, `1` failure (in `-p` parallel mode: `1` if any
   job failed).
 
 ## ODBC prerequisites (ODBC sources only)

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/README.md

@@ -2,6 +2,9 @@
 
 ## PING (ping-godhand)'s Universal Data Exporter
 
+> **Provided as-is. No support, no warranty, no roadmap commitments, use at
+> your own risk.**
+
 ## คำอธิบาย (ภาษาไทย)
 
 โปรแกรมช่วย Export ข้อมูลอย่างง่าย: เชื่อมต่อฐานข้อมูล รันคำสั่ง SQL
@@ -149,14 +152,14 @@ All options:
 | `-m` | `--mode` | export mode: `groupby` \| `date` \| `relativedate` \| `monthbydate` \| `splitrow` \| `watermark` — see section 4 |
 | `-col` | `--column` | column the mode partitions on |
 | `-row` | `--row` | rows per file (`-m splitrow`) |
-| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd` |
+| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd`; omitted with `-dr`/`-mr` ⇒ today (system date) |
 | `-dt` | `--dateto` | end date `yyyy-MM-dd` (`-m date`) |
 | `-dr` | `--daysrelative` | days back from `-df` (`-m relativedate`) |
 | `-mr` | `--monthsrelative` | months back from `-df` (`-m monthbydate`) |
 | `-rm` | `--removeexisting` | `Yes`: clear the output directory before exporting |
 | `-j` | `--job` | run one job.ini section — see section 5 |
 | `-jf` | `--jobfile` | job file path (default `./job.ini`) |
-| `-pl` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count) |
+| `-p` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count); `-pl` still works as a legacy alias |
 | `-n` | `--name` | job name shown in logs and the default log filename |
 | `-cf` | `--configfile` | config file path (default `./config.ini`) |
 | `-lf` | `--logfile` | log file path |
@@ -196,7 +199,8 @@ daily/
 └── sales_2026-01-05.csv
 ```
 
-**`relativedate` — N days back from an anchor date, anchor included:**
+**`relativedate` — N days back from an anchor date, anchor included
+(omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m relativedate -col txn_date \
@@ -211,7 +215,7 @@ rel/
 ```
 
 **`monthbydate` — N months back plus the anchor month (the anchor month stops
-at the anchor date):**
+at the anchor date; omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m monthbydate -col txn_date \
@@ -266,7 +270,7 @@ file — see *Output and logs* below):
 
 Put recurring exports in a job file so you never retype long commands. Each
 `[Section]` is **one job**: run one with `-j SectionName`, or all of them at
-once with `-pl`. Every key is simply a CLI option written as a config key:
+once with `-p`. Every key is simply a CLI option written as a config key:
 
 ```ini
 [DailySales]
@@ -290,7 +294,7 @@ Output=out/full_dump.parquet
 ```bash
 ping-dataexport -j DailySales                 # one section (job.ini by default, -jf elsewhere)
 ping-dataexport -j DailySales -od other_dir   # CLI options override the section
-ping-dataexport -pl 4                         # ALL sections in parallel, 4 workers
+ping-dataexport -p 4                          # ALL sections in parallel, 4 workers
 ```
 
 Every job.ini key and the CLI option it mirrors (keys are case-insensitive):
@@ -352,7 +356,7 @@ only, no metadata lookups.
 - Every run logs structured lines to stdout and to a log file:
   `-lf path` > `LogFile=` in config.ini > default
   `{ExportFolder}/logs/log_{jobname}.txt`.
-- CLI exit codes: `0` success, `1` failure (in `-pl` parallel mode: `1` if any
+- CLI exit codes: `0` success, `1` failure (in `-p` parallel mode: `1` if any
   job failed).
 
 ## ODBC prerequisites (ODBC sources only)

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ping-dataexport"
-version = "0.2.0"
-description = "Universal database data export to CSV/TXT/Parquet — streaming, typed, no pandas"
+version = "0.2.2"
+description = "PING's Data Export Tool - To Parquet/CSV/TEXT as Accelerator for Data & AI Project"
 readme = "README.md"
 license = "Apache-2.0"
 license-files = ["LICENSE"]

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/src/ping_dataexport/__init__.py

@@ -8,4 +8,4 @@ The package uses relative imports only and has no import-time side effects, so
 the directory can be copied into any project and imported directly.
 """
 
-__version__ = "0.2.0"
+__version__ = "0.2.2"

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/src/ping_dataexport/cli.py

@@ -91,7 +91,7 @@ def build_parser() -> argparse.ArgumentParser:
     p.add_argument("-lf", "--logfile", help="log file path")
     p.add_argument("-t", "--test", action="store_true", default=False,
                    help="test mode: preview only, no files")
-    p.add_argument("-pl", "--parallel", nargs="?", const=0, type=int, metavar="N",
+    p.add_argument("-p", "-pl", "--parallel", nargs="?", const=0, type=int, metavar="N",
                    help="run ALL job sections in parallel with N workers (default: CPU count)")
     return p
 

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/src/ping_dataexport/job/spec.py

@@ -169,8 +169,8 @@ class JobSpecBuilder:
 
         datefrom = parse_strict_date(datefrom_v, what="--datefrom") if datefrom_v else None
         dateto = parse_strict_date(dateto_v, what="--dateto") if dateto_v else None
-        if mode == "monthbydate" and datefrom is None:
-            datefrom = self.today  # anchor defaults to today
+        if mode in ("relativedate", "monthbydate") and datefrom is None:
+            datefrom = self.today  # -dr/-mr without -df: anchor = current system date
 
         output = layered("output")
         outputdir = layered("outputdir")

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2}/src/ping_dataexport/job/validator.py

@@ -45,7 +45,8 @@ class JobValidator:
                 e(spec, f"--datefrom {spec.datefrom} is after --dateto {spec.dateto}")
         if spec.mode == "relativedate":
             if not spec.datefrom or spec.daysrelative is None:
-                e(spec, "--mode relativedate requires --datefrom and --daysrelative")
+                e(spec, "--mode relativedate requires --daysrelative "
+                        "(--datefrom defaults to today when omitted)")
             if spec.daysrelative < 0:
                 e(spec, "--daysrelative must be >= 0")
         if spec.mode == "monthbydate":

{ping_dataexport-0.2.0 → ping_dataexport-0.2.2/src/ping_dataexport.egg-info}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: ping-dataexport
-Version: 0.2.0
-Summary: Universal database data export to CSV/TXT/Parquet — streaming, typed, no pandas
+Version: 0.2.2
+Summary: PING's Data Export Tool - To Parquet/CSV/TEXT as Accelerator for Data & AI Project
 Author: vorapol
 License-Expression: Apache-2.0
 Keywords: export,database,csv,parquet,etl,data-platform,airflow
@@ -31,6 +31,9 @@ Dynamic: license-file
 
 ## PING (ping-godhand)'s Universal Data Exporter
 
+> **Provided as-is. No support, no warranty, no roadmap commitments, use at
+> your own risk.**
+
 ## คำอธิบาย (ภาษาไทย)
 
 โปรแกรมช่วย Export ข้อมูลอย่างง่าย: เชื่อมต่อฐานข้อมูล รันคำสั่ง SQL
@@ -178,14 +181,14 @@ All options:
 | `-m` | `--mode` | export mode: `groupby` \| `date` \| `relativedate` \| `monthbydate` \| `splitrow` \| `watermark` — see section 4 |
 | `-col` | `--column` | column the mode partitions on |
 | `-row` | `--row` | rows per file (`-m splitrow`) |
-| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd` |
+| `-df` | `--datefrom` | start / anchor date `yyyy-MM-dd`; omitted with `-dr`/`-mr` ⇒ today (system date) |
 | `-dt` | `--dateto` | end date `yyyy-MM-dd` (`-m date`) |
 | `-dr` | `--daysrelative` | days back from `-df` (`-m relativedate`) |
 | `-mr` | `--monthsrelative` | months back from `-df` (`-m monthbydate`) |
 | `-rm` | `--removeexisting` | `Yes`: clear the output directory before exporting |
 | `-j` | `--job` | run one job.ini section — see section 5 |
 | `-jf` | `--jobfile` | job file path (default `./job.ini`) |
-| `-pl` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count) |
+| `-p` | `--parallel` | run ALL job sections in parallel with N workers (default: CPU count); `-pl` still works as a legacy alias |
 | `-n` | `--name` | job name shown in logs and the default log filename |
 | `-cf` | `--configfile` | config file path (default `./config.ini`) |
 | `-lf` | `--logfile` | log file path |
@@ -225,7 +228,8 @@ daily/
 └── sales_2026-01-05.csv
 ```
 
-**`relativedate` — N days back from an anchor date, anchor included:**
+**`relativedate` — N days back from an anchor date, anchor included
+(omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m relativedate -col txn_date \
@@ -240,7 +244,7 @@ rel/
 ```
 
 **`monthbydate` — N months back plus the anchor month (the anchor month stops
-at the anchor date):**
+at the anchor date; omit `-df` to anchor on today):**
 
 ```bash
 ping-dataexport -s DB01 -q "SELECT * FROM sales" -m monthbydate -col txn_date \
@@ -295,7 +299,7 @@ file — see *Output and logs* below):
 
 Put recurring exports in a job file so you never retype long commands. Each
 `[Section]` is **one job**: run one with `-j SectionName`, or all of them at
-once with `-pl`. Every key is simply a CLI option written as a config key:
+once with `-p`. Every key is simply a CLI option written as a config key:
 
 ```ini
 [DailySales]
@@ -319,7 +323,7 @@ Output=out/full_dump.parquet
 ```bash
 ping-dataexport -j DailySales                 # one section (job.ini by default, -jf elsewhere)
 ping-dataexport -j DailySales -od other_dir   # CLI options override the section
-ping-dataexport -pl 4                         # ALL sections in parallel, 4 workers
+ping-dataexport -p 4                          # ALL sections in parallel, 4 workers
 ```
 
 Every job.ini key and the CLI option it mirrors (keys are case-insensitive):
@@ -381,7 +385,7 @@ only, no metadata lookups.
 - Every run logs structured lines to stdout and to a log file:
   `-lf path` > `LogFile=` in config.ini > default
   `{ExportFolder}/logs/log_{jobname}.txt`.
-- CLI exit codes: `0` success, `1` failure (in `-pl` parallel mode: `1` if any
+- CLI exit codes: `0` success, `1` failure (in `-p` parallel mode: `1` if any
   job failed).
 
 ## ODBC prerequisites (ODBC sources only)