{"id":5154,"date":"2026-01-15T13:08:32","date_gmt":"2026-01-15T07:38:32","guid":{"rendered":"https:\/\/w3buddy.com\/?p=5154"},"modified":"2026-01-20T10:13:52","modified_gmt":"2026-01-20T04:43:52","slug":"oracle-ctas-complete-guide","status":"publish","type":"post","link":"https:\/\/w3buddy.com\/blog\/oracle-ctas-complete-guide\/","title":{"rendered":"Oracle CTAS: The Complete Guide to Copying Tables (With All Dependencies)"},"content":{"rendered":"\n

Most Oracle developers start with the basic table copy command:<\/p>\n\n\n\n

CREATE TABLE new_table AS SELECT * FROM old_table;\n<\/code><\/pre>\n\n\n\n
However, this only copies about 20% of what makes your table functional. If you’ve ever copied a table and wondered why your application broke, or why queries suddenly ran slower, or why data validation stopped working\u2014this guide is for you.<\/p>\n\n\n\n
\n\n\n\n
What Is CTAS (CREATE TABLE AS SELECT)?<\/h2>\n\n\n\n
CTAS<\/strong> is a DDL (Data Definition Language) command that creates a new table based on the result set of a SELECT query.<\/p>\n\n\n\n
What CTAS Can Do<\/h3>\n\n\n\n
First and foremost, it can copy complete table structure and data. Additionally, it allows you to copy filtered subsets of data and specific columns only. Moreover, you can create empty table structures, generate tables from complex joins and calculations, and perform quick data transformations.<\/p>\n\n\n\n
Basic Syntax<\/h3>\n\n\n\n
CREATE TABLE new_table_name\nAS\nSELECT column1, column2, ...\nFROM source_table\nWHERE conditions;\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7 Essential CTAS Scenarios (With Examples)<\/h2>\n\n\n\n
Scenario 1: Complete Table Copy (Structure + All Data)<\/h3>\n\n\n\n
Use Case:<\/strong> Quick backup or creating a testing copy<\/p>\n\n\n\n
CREATE TABLE employees_copy\nAS\nSELECT * FROM employees;\n<\/code><\/pre>\n\n\n\n
Verify the copy:<\/strong><\/p>\n\n\n\n
-- Check row counts match\nSELECT COUNT(*) FROM employees;\nSELECT COUNT(*) FROM employees_copy;\n\n-- Compare structure\nDESC employees;\nDESC employees_copy;\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Scenario 2: Copy Only Selected Columns<\/h3>\n\n\n\n
Use Case:<\/strong> Create simplified views for reporting or external systems<\/p>\n\n\n\n
CREATE TABLE employees_basic\nAS\nSELECT employee_id, first_name, last_name, email, hire_date\nFROM employees;\n<\/code><\/pre>\n\n\n\n
Verify columns:<\/strong><\/p>\n\n\n\n
DESC employees_basic;\nSELECT * FROM employees_basic WHERE ROWNUM <= 5;\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Scenario 3: Copy Structure Only (No Data)<\/h3>\n\n\n\n
Use Case:<\/strong> Create template tables for bulk loading or staging<\/p>\n\n\n\n
CREATE TABLE employees_staging\nAS\nSELECT * FROM employees WHERE 1=0;\n<\/code><\/pre>\n\n\n\n
The trick:<\/strong> WHERE 1=0<\/code> is always false, so zero rows are returned, but the structure is preserved.<\/p>\n\n\n\n
Verify it’s empty:<\/strong><\/p>\n\n\n\n
SELECT COUNT(*) FROM employees_staging;  -- Should return 0\nDESC employees_staging;  -- Should show all columns\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Scenario 4: Copy Filtered Data (WHERE Condition)<\/h3>\n\n\n\n
Use Case:<\/strong> Create department-specific tables or archive old records<\/p>\n\n\n\n
-- Copy only sales department employees\nCREATE TABLE employees_sales\nAS\nSELECT *\nFROM employees\nWHERE department_id = 80;\n\n-- Copy employees hired after 2020\nCREATE TABLE employees_recent\nAS\nSELECT *\nFROM employees\nWHERE hire_date >= DATE '2020-01-01';\n<\/code><\/pre>\n\n\n\n
Verify filtering:<\/strong><\/p>\n\n\n\n
SELECT COUNT(*), MIN(hire_date), MAX(hire_date) \nFROM employees_recent;\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Scenario 5: Copy With Calculated\/Derived Columns<\/h3>\n\n\n\n
Use Case:<\/strong> Precompute values for reporting tables<\/p>\n\n\n\n
CREATE TABLE employees_compensation\nAS\nSELECT \n    employee_id,\n    first_name,\n    last_name,\n    salary,\n    salary * 12 AS annual_salary,\n    salary * 12 * 0.15 AS estimated_tax,\n    ROUND(salary * 1.1, 2) AS projected_salary\nFROM employees;\n<\/code><\/pre>\n\n\n\n
Important Note:<\/strong> Calculated columns become regular columns\u2014formulas are not preserved.<\/p>\n\n\n\n
\n\n\n\n
Scenario 6: Copy Using JOINs (Multiple Tables)<\/h3>\n\n\n\n
Use Case:<\/strong> Create denormalized tables for analytics or reporting<\/p>\n\n\n\n
CREATE TABLE employee_department_summary\nAS\nSELECT \n    e.employee_id,\n    e.first_name,\n    e.last_name,\n    e.salary,\n    d.department_name,\n    d.location_id,\n    l.city,\n    l.country_id\nFROM employees e\nJOIN departments d ON e.department_id = d.department_id\nJOIN locations l ON d.location_id = l.location_id;\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Scenario 7: Copy Table to Another Schema<\/h3>\n\n\n\n
Use Case:<\/strong> Move data between environments or share data across schemas<\/p>\n\n\n\n
CREATE TABLE hr_backup.employees_archive\nAS\nSELECT * FROM hr.employees;\n<\/code><\/pre>\n\n\n\n
Prerequisites:<\/strong><\/p>\n\n\n\n
    \n
  • First, you must have CREATE TABLE<\/code> privilege in the target schema<\/li>\n\n\n\n
  • Second, you must have SELECT<\/code> privilege on the source table<\/li>\n\n\n\n
  • Finally, the target schema must exist<\/li>\n<\/ul>\n\n\n\n
    Grant required privileges:<\/strong><\/p>\n\n\n\n
    GRANT SELECT ON hr.employees TO hr_backup;\nGRANT CREATE TABLE TO hr_backup;\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    \u26a0\ufe0f CRITICAL: What CTAS Does NOT Copy<\/h2>\n\n\n\n
    Here’s where most developers get caught off guard. CTAS only copies the basic structure and data.<\/strong><\/p>\n\n\n\n
    Specifically, it does NOT<\/strong> copy:<\/p>\n\n\n\n
    What’s Missing<\/th>Impact<\/th><\/tr><\/thead>
    \u274c Primary Keys<\/td>No uniqueness enforcement<\/td><\/tr>
    \u274c Foreign Keys<\/td>No referential integrity<\/td><\/tr>
    \u274c Indexes<\/td>Massive performance degradation<\/strong><\/td><\/tr>
    \u274c Triggers<\/td>Business logic won’t execute<\/td><\/tr>
    \u274c Sequences<\/td>Auto-increment won’t work<\/td><\/tr>
    \u274c Grants\/Permissions<\/td>Security controls missing<\/td><\/tr>
    \u274c Check Constraints<\/td>Data validation disabled<\/td><\/tr>
    \u274c NOT NULL Constraints<\/td>Can insert invalid data<\/td><\/tr>
    \u274c Default Values<\/td>Columns won’t auto-populate<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Let’s fix each one systematically.<\/p>\n\n\n\n
    \n\n\n\n
    Step-by-Step: Recreating All Table Dependencies<\/h2>\n\n\n\n
    1. Check and Recreate Primary Keys<\/h3>\n\n\n\n
    Check existing primary key:<\/strong><\/p>\n\n\n\n
    SELECT constraint_name, constraint_type, search_condition\nFROM user_constraints\nWHERE table_name = 'EMPLOYEES';\n<\/code><\/pre>\n\n\n\n
    Constraint types:<\/strong><\/p>\n\n\n\n
      \n
    • P<\/code> \u2192 Primary Key<\/li>\n\n\n\n
    • R<\/code> \u2192 Foreign Key (Referential)<\/li>\n\n\n\n
    • C<\/code> \u2192 Check Constraint<\/li>\n\n\n\n
    • U<\/code> \u2192 Unique Constraint<\/li>\n<\/ul>\n\n\n\n
      Recreate primary key:<\/strong><\/p>\n\n\n\n
      ALTER TABLE employees_copy\nADD CONSTRAINT emp_copy_pk PRIMARY KEY (employee_id);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      2. Check and Recreate Foreign Keys<\/h3>\n\n\n\n
      Check foreign keys:<\/strong><\/p>\n\n\n\n
      SELECT \n    a.constraint_name,\n    a.table_name,\n    a.column_name,\n    c_pk.table_name AS references_table,\n    c_pk.constraint_name AS references_constraint\nFROM user_cons_columns a\nJOIN user_constraints c ON a.constraint_name = c.constraint_name\nJOIN user_constraints c_pk ON c.r_constraint_name = c_pk.constraint_name\nWHERE c.constraint_type = 'R'\nAND a.table_name = 'EMPLOYEES';\n<\/code><\/pre>\n\n\n\n
      Recreate foreign key:<\/strong><\/p>\n\n\n\n
      ALTER TABLE employees_copy\nADD CONSTRAINT emp_copy_dept_fk \nFOREIGN KEY (department_id) \nREFERENCES departments(department_id);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      3. Check and Recreate Indexes<\/h3>\n\n\n\n
      This is CRITICAL for performance.<\/strong><\/p>\n\n\n\n
      Check all indexes:<\/strong><\/p>\n\n\n\n
      SELECT \n    i.index_name,\n    i.uniqueness,\n    ic.column_name,\n    ic.column_position\nFROM user_indexes i\nJOIN user_ind_columns ic ON i.index_name = ic.index_name\nWHERE i.table_name = 'EMPLOYEES'\nORDER BY i.index_name, ic.column_position;\n<\/code><\/pre>\n\n\n\n
      Recreate regular index:<\/strong><\/p>\n\n\n\n
      CREATE INDEX emp_copy_email_idx \nON employees_copy(email);\n<\/code><\/pre>\n\n\n\n
      Recreate composite index:<\/strong><\/p>\n\n\n\n
      CREATE INDEX emp_copy_dept_sal_idx \nON employees_copy(department_id, salary);\n<\/code><\/pre>\n\n\n\n
      Recreate unique index:<\/strong><\/p>\n\n\n\n
      CREATE UNIQUE INDEX emp_copy_email_unq \nON employees_copy(email);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      4. Check and Recreate Triggers<\/h3>\n\n\n\n
      Check triggers:<\/strong><\/p>\n\n\n\n
      SELECT trigger_name, trigger_type, triggering_event, status\nFROM user_triggers\nWHERE table_name = 'EMPLOYEES';\n<\/code><\/pre>\n\n\n\n
      Get trigger code:<\/strong><\/p>\n\n\n\n
      SELECT trigger_body\nFROM user_triggers\nWHERE trigger_name = 'EMP_AUDIT_TRG';\n<\/code><\/pre>\n\n\n\n
      Recreate trigger:<\/strong><\/p>\n\n\n\n
      CREATE OR REPLACE TRIGGER emp_copy_audit_trg\nBEFORE INSERT OR UPDATE ON employees_copy\nFOR EACH ROW\nBEGIN\n    :NEW.last_modified := SYSDATE;\nEND;\n\/\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      5. Check and Recreate Sequences<\/h3>\n\n\n\n
      Check sequences:<\/strong><\/p>\n\n\n\n
      SELECT sequence_name, last_number, increment_by\nFROM user_sequences\nWHERE sequence_name LIKE '%EMP%';\n<\/code><\/pre>\n\n\n\n
      Get current sequence value:<\/strong><\/p>\n\n\n\n
      SELECT emp_seq.CURRVAL FROM dual;\n<\/code><\/pre>\n\n\n\n
      Recreate sequence (starting from current value):<\/strong><\/p>\n\n\n\n
      CREATE SEQUENCE emp_copy_seq\nSTART WITH 1000\nINCREMENT BY 1\nNOCACHE;\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      6. Check and Recreate Grants<\/h3>\n\n\n\n
      Check existing permissions:<\/strong><\/p>\n\n\n\n
      SELECT grantee, privilege, grantable\nFROM user_tab_privs\nWHERE table_name = 'EMPLOYEES';\n<\/code><\/pre>\n\n\n\n
      Reapply grants:<\/strong><\/p>\n\n\n\n
      GRANT SELECT, INSERT, UPDATE ON employees_copy TO app_user;\nGRANT SELECT ON employees_copy TO reporting_user;\nGRANT ALL PRIVILEGES ON employees_copy TO admin_user;\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      7. Check and Recreate Check Constraints<\/h3>\n\n\n\n
      Check constraints:<\/strong><\/p>\n\n\n\n
      SELECT constraint_name, search_condition\nFROM user_constraints\nWHERE table_name = 'EMPLOYEES'\nAND constraint_type = 'C'\nAND constraint_name NOT LIKE 'SYS%';  -- Exclude system-generated\n<\/code><\/pre>\n\n\n\n
      Recreate check constraints:<\/strong><\/p>\n\n\n\n
      ALTER TABLE employees_copy\nADD CONSTRAINT emp_copy_salary_chk CHECK (salary > 0);\n\nALTER TABLE employees_copy\nADD CONSTRAINT emp_copy_email_chk CHECK (email LIKE '%@%');\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      8. Check and Recreate NOT NULL Constraints<\/h3>\n\n\n\n
      Check NOT NULL constraints:<\/strong><\/p>\n\n\n\n
      SELECT column_name, nullable\nFROM user_tab_columns\nWHERE table_name = 'EMPLOYEES'\nAND nullable = 'N';\n<\/code><\/pre>\n\n\n\n
      Apply NOT NULL:<\/strong><\/p>\n\n\n\n
      ALTER TABLE employees_copy\nMODIFY (email NOT NULL);\n\nALTER TABLE employees_copy\nMODIFY (employee_id NOT NULL);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      9. Check and Recreate Default Values<\/h3>\n\n\n\n
      Check default values:<\/strong><\/p>\n\n\n\n
      SELECT column_name, data_default\nFROM user_tab_columns\nWHERE table_name = 'EMPLOYEES'\nAND data_default IS NOT NULL;\n<\/code><\/pre>\n\n\n\n
      Apply defaults:<\/strong><\/p>\n\n\n\n
      ALTER TABLE employees_copy\nMODIFY (hire_date DEFAULT SYSDATE);\n\nALTER TABLE employees_copy\nMODIFY (status DEFAULT 'ACTIVE');\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      \ud83d\udea8 Common CTAS Mistakes to Avoid<\/h2>\n\n\n\n
      Mistake #1: Assuming Constraints Are Copied<\/h3>\n\n\n\n
      -- \u274c WRONG: Thinking this copies everything\nCREATE TABLE users_backup AS SELECT * FROM users;\n-- Now trying to insert duplicate IDs succeeds (no PK!)\n<\/code><\/pre>\n\n\n\n
      Mistake #2: Forgetting Indexes<\/h3>\n\n\n\n
      -- \u274c WRONG: Copying large table without indexes\nCREATE TABLE sales_archive AS SELECT * FROM sales;\n-- Queries on sales_archive are now 100x slower\n<\/code><\/pre>\n\n\n\n
      Mistake #3: Using CTAS for Production Replication<\/h3>\n\n\n\n
      -- \u274c WRONG: Using CTAS for ongoing replication\nCREATE TABLE live_backup AS SELECT * FROM live_data;\n-- Triggers, sequences, and constraints are missing\n<\/code><\/pre>\n\n\n\n
      Mistake #4: Not Validating Data Types<\/h3>\n\n\n\n
      -- \u274c WRONG: Not checking if calculated columns have correct types\nCREATE TABLE report AS \nSELECT salary * 12 AS annual FROM employees;\n-- annual might be NUMBER instead of NUMBER(10,2)\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      \u2705 Best Practices for Using CTAS<\/h2>\n\n\n\n
      1. Always Verify After Creation<\/h3>\n\n\n\n
      First, check the structure to ensure all columns are present:<\/p>\n\n\n\n
      -- Check structure\nDESC employees_copy;\n\n-- Check row count\nSELECT COUNT(*) FROM employees_copy;\n\n-- Compare with original\nSELECT COUNT(*) FROM employees;\n<\/code><\/pre>\n\n\n\n
      2. Use Clear Naming Conventions<\/h3>\n\n\n\n
      Moreover, establish consistent naming patterns for different table types:<\/p>\n\n\n\n
        \n
      • _copy<\/code> \u2192 Exact copy for testing<\/li>\n\n\n\n
      • _bak<\/code> \u2192 Backup before changes<\/li>\n\n\n\n
      • _staging<\/code> \u2192 Temporary staging table<\/li>\n\n\n\n
      • _archive<\/code> \u2192 Historical data archive<\/li>\n\n\n\n
      • _temp<\/code> \u2192 Temporary working table<\/li>\n<\/ul>\n\n\n\n
        3. Document What’s Missing<\/h3>\n\n\n\n
        Furthermore, always add comments to track what needs recreation:<\/p>\n\n\n\n
        -- Add comment to table\nCOMMENT ON TABLE employees_copy IS \n'Copy of employees table created 2026-01-15. Missing: PKs, FKs, triggers, indexes';\n<\/code><\/pre>\n\n\n\n
        4. Use CTAS Appropriately<\/h3>\n\n\n\n
        Good use cases:<\/strong><\/p>\n\n\n\n
        Initially, CTAS works well for quick backups before major changes. Subsequently, it’s perfect for creating test datasets and staging tables for ETL processes. Additionally, it’s ideal for ad-hoc reporting tables and data archival.<\/p>\n\n\n\n
        Bad use cases:<\/strong><\/p>\n\n\n\n
        Conversely, avoid using CTAS for production data replication. Similarly, don’t use it when creating tables with complex business logic. Finally, it’s not suitable when you need all constraints and dependencies.<\/p>\n\n\n\n
        \n\n\n\n
        \ud83d\udccb Complete Post-CTAS Checklist<\/h2>\n\n\n\n
        After running CTAS, systematically check everything:<\/p>\n\n\n\n
        -- 1. Structure verification\nDESC table_name;\n\n-- 2. Row count\nSELECT COUNT(*) FROM table_name;\n\n-- 3. Constraints\nSELECT constraint_name, constraint_type \nFROM user_constraints \nWHERE table_name = 'TABLE_NAME';\n\n-- 4. Indexes\nSELECT index_name, column_name \nFROM user_ind_columns \nWHERE table_name = 'TABLE_NAME';\n\n-- 5. Triggers\nSELECT trigger_name, status \nFROM user_triggers \nWHERE table_name = 'TABLE_NAME';\n\n-- 6. Grants\nSELECT grantee, privilege \nFROM user_tab_privs \nWHERE table_name = 'TABLE_NAME';\n\n-- 7. Sequences (if applicable)\nSELECT sequence_name \nFROM user_sequences;\n\n-- 8. NOT NULL constraints\nSELECT column_name \nFROM user_tab_columns \nWHERE table_name = 'TABLE_NAME' AND nullable = 'N';\n\n-- 9. Default values\nSELECT column_name, data_default \nFROM user_tab_columns \nWHERE table_name = 'TABLE_NAME' AND data_default IS NOT NULL;\n<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        \ud83c\udfaf Complete Example: Full Table Copy with All Dependencies<\/h2>\n\n\n\n
        Here’s a complete workflow for copying a table with all its dependencies:<\/p>\n\n\n\n
        -- Step 1: Copy the data\nCREATE TABLE employees_backup AS SELECT * FROM employees;\n\n-- Step 2: Add primary key\nALTER TABLE employees_backup\nADD CONSTRAINT emp_bak_pk PRIMARY KEY (employee_id);\n\n-- Step 3: Add foreign keys\nALTER TABLE employees_backup\nADD CONSTRAINT emp_bak_dept_fk \nFOREIGN KEY (department_id) REFERENCES departments(department_id);\n\n-- Step 4: Recreate indexes\nCREATE INDEX emp_bak_email_idx ON employees_backup(email);\nCREATE INDEX emp_bak_dept_idx ON employees_backup(department_id);\n\n-- Step 5: Add check constraints\nALTER TABLE employees_backup\nADD CONSTRAINT emp_bak_salary_chk CHECK (salary > 0);\n\n-- Step 6: Apply NOT NULL constraints\nALTER TABLE employees_backup\nMODIFY (email NOT NULL);\n\n-- Step 7: Grant permissions\nGRANT SELECT ON employees_backup TO reporting_user;\n\n-- Step 8: Verify everything\nSELECT 'Original count: ' || COUNT(*) FROM employees\nUNION ALL\nSELECT 'Backup count: ' || COUNT(*) FROM employees_backup;\n<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        Alternative: Using Oracle Data Pump for Complete Copies<\/h2>\n\n\n\n
        If you need everything<\/strong> copied (including all dependencies), consider using Oracle Data Pump instead:<\/p>\n\n\n\n
        -- Export\nexpdp username\/password TABLES=employees DIRECTORY=dump_dir DUMPFILE=emp.dmp\n\n-- Import with new name\nimpdp username\/password TABLES=employees DIRECTORY=dump_dir DUMPFILE=emp.dmp REMAP_TABLE=employees:employees_copy\n<\/code><\/pre>\n\n\n\n
        Data Pump copies:<\/strong><\/p>\n\n\n\n
        Notably, Data Pump handles all constraints automatically. In addition, it preserves all indexes and triggers. Furthermore, it maintains grants and privileges along with statistics.<\/p>\n\n\n\n
        \n\n\n\n
        Final Thoughts<\/h2>\n\n\n\n
        CREATE TABLE AS SELECT is one of Oracle’s fastest and most powerful commands\u2014but only when you understand its limitations.<\/p>\n\n\n\n
        Remember the golden rule:<\/strong> CTAS copies data and basic structure. Everything else must be recreated manually.<\/p>\n\n\n\n
        Consequently, master CTAS by:<\/p>\n\n\n\n
          \n
        1. Knowing exactly what it copies (data + column definitions)<\/li>\n\n\n\n
        2. Understanding what it skips (everything else!)<\/li>\n\n\n\n
        3. Having a systematic process to verify and recreate dependencies<\/li>\n<\/ol>\n\n\n\n
          Therefore, use this guide as your reference, bookmark it, and never lose data integrity when copying tables again.<\/p>\n\n\n\n
          \n\n\n\n
          Pro Tip:<\/strong> Create a script template that includes all verification queries and store it in your code repository. Then, every time you use CTAS, run through the complete checklist\u2014it takes 2 minutes and prevents hours of debugging later.<\/p>\n","protected":false},"excerpt":{"rendered":"
          Most Oracle developers start with the basic table copy command: However, this only copies about 20% of what makes your table functional. If you’ve ever copied a table and wondered why your application broke, or why queries suddenly ran slower, or why data validation stopped working\u2014this guide is for you. What Is CTAS (CREATE TABLE […]<\/p>\n","protected":false},"author":1,"featured_media":5156,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"googlesitekit_rrm_CAowu461DA:productID":"","footnotes":""},"categories":[1225],"tags":[],"class_list":["post-5154","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database"],"_links":{"self":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/posts\/5154","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/comments?post=5154"}],"version-history":[{"count":1,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/posts\/5154\/revisions"}],"predecessor-version":[{"id":5155,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/posts\/5154\/revisions\/5155"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/media\/5156"}],"wp:attachment":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/media?parent=5154"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/categories?post=5154"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/tags?post=5154"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}