Oneseco Media GITHUB

Tables are where you store your data. Tables are similar to excel spreadsheets. They contain columns and rows. For example, this table has 3 "columns" (id, name, description) and 4 "rows" of data: idnamedescription1The Phantom MenaceTwo Jedi escape a hostile blockade to find allies and come across a young boy who may bring balance to the Force.2Attack of the ClonesTen years after the invasion of Naboo, the Galactic Republic is facing a Separatist movement.3Revenge of the SithAs Obi-Wan pursues a new threat, Anakin acts as a double agent between the Jedi Council and Palpatine and is lured into a sinister plan to rule the galaxy.4Star WarsLuke Skywalker joins forces with a Jedi Knight, a cocky pilot, a Wookiee and two droids to save the galaxy from the Empire's world-destroying battle station. There are a few important differences from a spreadsheet, but it's a good starting point if you're new to Relational databases. Creating tables# When creating a table, it's best practice to add columns at the same time. You must define the "data type" of each column when it is created. You can add and remove columns at any time after creating a table. Supabase provides several options for creating tables. You can use the Dashboard or create them directly using SQL. We provide a SQL editor within the Dashboard, or you can connect to your database and run the SQL queries yourself. DashboardSQL Go to the Table Editor page in the Dashboard. Click New Table and create a table with the name todos. Click Save. Click New Column and create a column with the name task and type text. Click Save. When naming tables, use lowercase and underscores instead of spaces (e.g., table_name, not Table Name). Columns# You must define the "data type" when you create a column. Data types# Every column is a predefined type. Postgres provides many default types, and you can even design your own (or use extensions) if the default types don't fit your needs. You can use any data type that Postgres supports via the SQL editor. We only support a subset of these in the Table Editor in an effort to keep the experience simple for people with less experience with databases. Show/Hide default data typesNameAliasesDescriptionbigintint8signed eight-byte integerbigserialserial8autoincrementing eight-byte integerbitfixed-length bit stringbit varyingvarbitvariable-length bit stringbooleanboollogical Boolean (true/false)boxrectangular box on a planebyteabinary data (“byte array”)charactercharfixed-length character stringcharacter varyingvarcharvariable-length character stringcidrIPv4 or IPv6 network addresscirclecircle on a planedatecalendar date (year, month, day)double precisionfloat8double precision floating-point number (8 bytes)inetIPv4 or IPv6 host addressintegerint, int4signed four-byte integerinterval [ fields ]time spanjsontextual JSON datajsonbbinary JSON data, decomposedlineinfinite line on a planelsegline segment on a planemacaddrMAC (Media Access Control) addressmacaddr8MAC (Media Access Control) address (EUI-64 format)moneycurrency amountnumericdecimalexact numeric of selectable precisionpathgeometric path on a planepg_lsnPostgres Log Sequence Numberpg_snapshotuser-level transaction ID snapshotpointgeometric point on a planepolygonclosed geometric path on a planerealfloat4single precision floating-point number (4 bytes)smallintint2signed two-byte integersmallserialserial2autoincrementing two-byte integerserialserial4autoincrementing four-byte integertextvariable-length character stringtime [ without time zone ]time of day (no time zone)time with time zonetimetztime of day, including time zonetimestamp [ without time zone ]date and time (no time zone)timestamp with time zonetimestamptzdate and time, including time zonetsquerytext search querytsvectortext search documenttxid_snapshotuser-level transaction ID snapshot (deprecated; see pg_snapshot)uuiduniversally unique identifierxmlXML data You can "cast" columns from one type to another, however there can be some incompatibilities between types. For example, if you cast a timestamp to a date, you will lose all the time information that was previously saved. Primary keys# A table can have a "primary key" - a unique identifier for every row of data. A few tips for Primary Keys: It's recommended to create a Primary Key for every table in your database. You can use any column as a primary key, as long as it is unique for every row. It's common to use a uuid type or a numbered identity column as your primary key. 1create table movies (2 id bigint generated always as identity primary key3); In the example above, we have: created a column called id assigned the data type bigint instructed the database that this should be generated always as identity, which means that Postgres will automatically assign a unique number to this column. Because it's unique, we can also use it as our primary key. We could also use generated by default as identity, which would allow us to insert our own unique values.

It all starts with an API key Integrate Gemini's advanced AI into your applications Hello Kelvin, Ready to bring Gemini's power to your own applications? Get your API key and start building today. A Gemini API key allows you to: Easily integrate SDKs Leverage our comprehensive documentation to seamlessly incorporate Gemini into your projects. Control your output with system instructions and JSON mode Guide the model's behavior and ensure structured responses. Get production-ready with billing and cost optimization Scale your applications confidently with pay-as-you-go options and tools to help you manage costs effectively. Customize and fine-tune models Tailor Gemini models to your specific use cases and domains for optimal performance. Create real-time interactions with function calling Integrate external data sources and services for more dynamic and contextual responses. Get API key Next steps: Secure your key and start building First, ensure your API key is verified and securely stored. Then, let the Gemini API Cookbook be your guide. Explore code examples, learn prompt crafting techniques, and get inspired by real-world use cases. Need language-specific help? Check out our Gemini API quickstart. Join the Google AI Forum to ask questions and get help from other developers. Explore more resources: Prompting: Resources and tips for success Intro to prompting To get the most out of prompting, be sure to give clear instructions, define the task, and specify your constraints and response format. Check out these resources to find out more: • Get started: Intro to prompting • For best practices: Prompt strategies • For inspiration: Prompt Gallery • Join the community: Google AI discussion forum Fine-tune your model to suit your needs Intro to Fine-tuning Model tuning allows you to tailor Gemini to work with your unique dataset, and customize output to match your exact specifications. Try the simple 3-step process to fine-tune your model. Or, if you're ready to experiment now, explore our Model Tuning Guide. Unlock premium AI capabilities at a price that's right for you Exclusive features Along with free of charge versions*, Google Gemini offers pay-as-you-go plans with benefits like increased rate limits, reduced pricing for cached tokens, and protected data usage. *subject to rate limits; capacity not guaranteed. Thanks, Your Google AI Studio team Create prompt Get API Key Read the docs Join the conversation on the #gemini-api channel © 2025 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA This email was sent to [email protected] because you signed up to receive emails about Google AI. If you do not wish to receive these emails, please unsubscribe.