Event management sample database — MongoDB, flat (4,021 rows)

A collection per table. Each primary key is the document _id; foreign keys are fields under their own names, so the SQL version's joins become $lookup stages.

Load it:
  sh import.sh                    (into mongodb://localhost:27017)
  sh import.sh "<connection string>"

Or one collection at a time: mongoimport --db event-management --collection <name> --file <name>.ndjson

Collections:
  applied_coupons — 100 documents
  booth_assignments — 10 documents
  booths — 400 documents
  categories — 12 documents
  checkins — 600 documents
  coupons — 40 documents
  equipment — 60 documents
  event_categories — 10 documents
  event_sponsors — 10 documents
  event_vendors — 10 documents
  events — 10 documents
  exhibitors — 10 documents
  feedbacks — 40 documents
  media — 10 documents
  notifications — 30 documents
  payments — 1,000 documents
  profiles — 40 documents
  registrations — 1,000 documents
  roles — 4 documents
  rooms — 150 documents
  session_equipment — 10 documents
  session_speakers — 10 documents
  sessions — 10 documents
  speakers — 200 documents
  sponsors — 40 documents
  sponsorship_packages — 10 documents
  staff_assignments — 10 documents
  tasks — 10 documents
  tickets — 10 documents
  user_roles — 10 documents
  users — 80 documents
  vendors — 50 documents
  venues — 25 documents

Types: numeric columns are Decimal128, so totals stay exact; dates and timestamps are
Date values read as UTC (the data has no time zone); times and UUIDs are strings;
JSON columns are embedded objects.

Synthetic data, CC0-1.0, from databasesample.com. The same rows as the SQL and CSV files.
