Login

u/wraithWeaver

▲ 21 r/oraclecloud

Has anyone found a real workaround for the recent ~50 Mbps cap on Always-Free A1.Flex?

I tested multiple instances in Singapore, across different tenancies, and they all now sit around 45-55 Mbps. Single stream, multi-stream, upload, download, different test destinations — all hit the same ceiling.

This used to be much faster for me before, so it looks like an OCI-side throttle rather than anything inside the VM.

I also found this recent Oracle forum post with the same symptoms in Mumbai: https://community.oracle.com/customerconnect/discussion/949961/vm-standard-a1-flex-in-ap-mumbai-1-stuck-at-50-mbps-public-internet-despite-4-gbps-advertised

Question for people who have already dealt with this:

Did converting to Pay-As-You-Go actually remove the cap while keeping Always-Free usage free?

Did anyone get Oracle support to lift it?

Any other workaround besides moving to another provider?

Trying to decide whether it’s worth upgrading the tenancy or if I should just migrate off OCI.

reddit.com
u/wraithWeaver — 12 days ago
▲ 2 r/SQL

What features do you wish SQL clients handled better?

I’ve been building an open-source database client called Tablio, and one area I’m trying to improve is the SQL workflow itself: editor autocomplete, query history, pinned queries, explain-plan visualization, inline result search, JSON inspection, and cross-database behavior.

For people who write SQL daily across PostgreSQL, MySQL, SQL Server, SQLite, etc., what do you feel most database clients still get wrong?

Project/article for context: https://medium.com/@dasunnimantha777/tablio-a-fast-native-open-source-database-client-for-modern-database-workflows-211ae3530334

u/wraithWeaver — 13 days ago
▲ 2 r/SideProject

Hey everyone,

For the last several months I've been building Tablio, an open-source desktop database client written in Rust + Tauri with a React/TypeScript frontend. I wanted to share it here because it's finally at a point where it's genuinely useful day-to-day, not just a weekend prototype.

Why another DB client?

I'd been bouncing between DBeaver, DataGrip, TablePlus, pgAdmin, MySQL Workbench, and Azure Data Studio. Each one helped in some way, but I kept hitting the same friction:

  • Some are heavy enough that I don't want to keep them open all day
  • Inconsistent / no inline text search inside large result grids
  • Weak JSON viewers/editors
  • No real theming, or themes that don't extend everywhere
  • Editor experience that doesn't feel like a real editor (missing IntelliSense-style help, history, pinning)
  • Awkward when you're moving between Postgres, MySQL, SQL Server, SQLite, CockroachDB, TiDB, and Cassandra-family in the same hour

So I started building the tool I actually wanted.

What's in it right now

  • Rust backend handles all DB drivers, connection pooling, backups, exports, SSH tunneling — frontend stays thin
  • Native installers for Windows (.msi/.exe), macOS (Intel + Apple Silicon .dmg), and Linux (.deb, .rpm, .AppImage)
  • Tabbed workspace across multiple databases at the same time, connections organizable into colored folders
  • Data grid with inline editing, single-transaction save, inline text search, JSON inspection, primary/foreign key badges, generated test rows based on column types
  • Monaco-based SQL editor with autocomplete, formatting, query history, pinned queries, saved queries, EXPLAIN + visual plan
  • Server-side views: query stats (pg_stat_statements), active sessions, locks, server config, table stats
  • Postgres-style partition awareness (parents, children, default partitions, bounds)
  • Native pg_dump / pg_restore / mysqldump integration plus a dump-and-restore flow between Postgres connections
  • SSH tunneling (in-process, with known_hosts management UI and host-key mismatch prompts)
  • Visibility-aware polling so minimized windows aren't burning CPU

Why Rust + Tauri?

I didn't want to ship another Electron-class app for something users keep open all day. Tauri gives a native shell + small binaries, Rust gives me a solid place to put driver code, connection management, and anything that touches the filesystem or subprocesses. The CI matrix runs against real Postgres, MySQL, MariaDB, CockroachDB, TiDB, SQLite, Cassandra, ScyllaDB, and SQL Server containers — not mocks.

Links

Contributions wanted

There are a lot of things one person can't move on alone — especially per-engine work (e.g., bringing query stats parity to MySQL/MariaDB/MSSQL, more backup coverage, more keyboard-first workflows, theming, JSON editor improvements). If you work with databases and any of this resonates, issues and PRs are very welcome. Even bug reports with reproduction steps help a lot.

Happy to answer questions, take criticism, and hear what's missing for your workflow.

u/wraithWeaver — 13 days ago