The spreadsheet-like view allows you to edit the table directly without having to write queries. One of my favorite examples is the inline edit. TablePlus just takes into account so many little things that happen when you work with databases, which means, the team really pay attention to the details and the experience is very intuitive.
#Tableplus create table pro#
You can see clearly while browsing the database, switching between two tables would take a couple seconds for Sequel Pro with a loading sign. It’s fast to launch and doesn’t leave much memory footprint. TablePlus was built on top of Swift, Objective-C, C/C++, Perl for OSX allowing the app to take advantage of the native elements of the system to provide a very fast experience. I can use it to manage databases, tables, structures, indexes… For me, it provides a well-rounded solution to work with MySQL. It’s very easy to set up and get direct access to the MySQL databases on local and remote servers. It’s fast, easy to use, stable, and open source. I work with MySQL a lot, and I indeed need a really good client for MySQL. So I gave it a try and to my surprise, TablePlus is such a brilliant app that boosts my productivity so much. But recently, one of my friends recommended to try out TablePlus and he referred it as the best MySQL GUI Tool. I’ve been a loyal fan of Sequel Pro for almost 7 years and that was a fantastic experience. Because if I change nothing, I will learn nothing, or if I change too much at a time, that can potentially be a mess. Why I looked for an alternative?Įvery once in a while, I try to change a couple things when I work, that can be a new tool or a new technique. I was also somewhat abusing Redis for my guestbook, where SQL is a better fit.TablePlus is a modern, native SQL client with intuitive GUI tools to create, access, query & edit multiple relational databases such as MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Amazon Redshift, MariaDB, CockroachDB, Vertica, and Redis.
#Tableplus create table code#
Having one service instead of two cleaned up the code and required fewer environment variables to connect to each service. I'm pleased with the results of the migration. This has been significantly faster than my previous Firebase implementation.
For the last week, I've seen latency of ~150ms for my Next.js API Routes, deployed as serverless functions on Vercel in us-east.
Checkly allows me to set alerts if there's downtime or if performance decreases below my accepted threshold. I've been monitoring the performance of my production APIs connecting to PlanetScale with Checkly. Pages/api/migrate-redis.js import db from 'lib/planetscale' import guestbookData from 'data/guestbook' export default async function handler ( req, res ) ĬREATE TABLE ` views ` ( `slug` varchar ( 128 ) NOT NULL, `count` bigint NOT NULL DEFAULT '1', PRIMARY KEY ( `slug` ) ) CREATE TABLE ` guestbook ` ( `id` bigint NOT NULL AUTO_INCREMENT, `email` varchar ( 256 ) NOT NULL, `body` varchar ( 500 ) NOT NULL, `created_by` varchar ( 256 ) NOT NULL, `created_at` datetime ( 6 ) NOT NULL DEFAULT CURRENT_TIMESTAMP ( 6 ), `updated_at` datetime ( 6 ) NOT NULL DEFAULT CURRENT_TIMESTAMP ( 6 ), PRIMARY KEY ( `id` ) ) Results
#Tableplus create table how to#
I even created a course showing how to use Firebase with Next.js, if you're interested. I learn best by experimenting and building. The primary decision for choosing these technologies was to learn. This site previously used Firebase and Redis for real-time blog post views and my guestbook. I had a chance to talk with Nick from PlanetScale on a stream last month if you want to see a live demo of the workflow. Now, after using it for a few weeks and monitoring performance, I'm seeing APIs resolve in ~150ms on average (see results below).
0 kommentar(er)
