Rails does not add new tables to schema.rb in non public schema

In Rails, when you create new tables in a non-public schema (i.e., a schema other than the default "public" schema) in PostgreSQL, Rails may not automatically add those new tables to the schema.rb file. This behavior is due to the way Rails generates the schema file, and it's intended to avoid potential issues with other databases that do not support multiple schemas.

To address this, you can manually include the tables from the non-public schema in the schema.rb file. Here's how you can do it:

1. Manually Include Tables in schema.rb: Open the schema.rb file located in the db folder of your Rails application. You should see the schema definition for your default "public" schema. To include tables from a non-public schema, you can add a custom SQL statement in the schema.rb file.

For example, let's say you have a table named "my_table" in a non-public schema named "my_schema." To include it in the schema.rb, you can add the following line:

rubyCopy code
# db/schema.rb

ActiveRecord::Schema.define(version: 2023_07_19_000000) do
  # ... existing schema definition ...

  # Include the table from the non-public schema
  execute("SET search_path TO my_schema, public;") # Set the schema search path
  create_table "my_table", force: :cascade do |t|
    # ... table columns ...
  end
end

The execute method is used to set the search path to the non-public schema temporarily and then create the table within that schema. After this, Rails will recognize the table when running database tasks and migrations.

2. Running Migrations: If you plan to run database migrations that involve the non-public schema, ensure you set the correct schema search path in your migrations:

rubyCopy code
# db/migrate/your_migration_file.rb

class YourMigration < ActiveRecord::Migration[6.1]
  def up
    # Set the schema search path to include the non-public schema
    execute("SET search_path TO my_schema, public;")

    # Your migration logic here
    create_table "my_table", force: :cascade do |t|
      # ... table columns ...
    end
  end

  def down
    drop_table "my_table"
  end
end

With this approach, the table and other objects in the non-public schema will be included in the schema.rb file, and Rails will recognize them properly during database tasks.

Remember that including tables from non-public schemas in the schema.rb file is specific to PostgreSQL databases. Other databases may not support multiple schemas, so the inclusion of tables from non-default schemas may cause issues with schema management in those databases.

Before proceeding, ensure that including tables from non-public schemas is the appropriate solution for your specific application requirements and database setup.