in airbyte connection setup, we declare the source and destination, in that while declaring thesource we are supposed to decalre the source database, source schema, and the target table, now if I keep on changing the source database schema repeatedly and trigger the connection, then the connection would work well, taking the new source databse schema and table correctly, or it is not recommended

Airbyte handles schema changes in the source database based on the connection settings you've configured. By default, Airbyte continues to sync data using the configured schema until that schema is updated. If a field is renamed or deleted in the source, that field will no longer be replicated, but all remaining fields will. The schema can only be updated manually in the UI (by clicking “Update Schema” in the settings page for the connection). When a schema is updated, Airbyte will re-sync all data for that source using the new schema[^1^]. Airbyte offers a few options for how it should detect and propagate schema changes. Depending on how you configure it, Airbyte can automatically sync any detected schema changes or ignore them[^2^]. - Propagate field changes only: Only column changes will be propagated. New or removed streams will be ignored. - Propagate all field and stream changes: All new streams and column changes from the source will automatically be propagated and reflected in the destination. This includes stream changes (additions or deletions), column changes (additions or deletions) and data type changes. - Approve all changes myself: This allows you to detect and manually approve changes. Schema changes will be detected, but not propagated. Syncs will continue running with the schema you've set up. To propagate the detected schema changes, you will need to approve the changes manually. - Stop future syncs: Connections will be automatically paused as soon as any schema changes are detected[^2^]. However, it's important to note that dynamic schema change is not currently supported by Airbyte[^3^]. Your connector must be able to know the schema of the records it will handle before running a replication[^3^]. If you're frequently changing your source database schema, you might want to keep an eye on the ongoing work on schema evolution feature[^1^][^3^]. [^1^]: [Forum Post: How does Airbyte handle replication when a data source changes its schema?](https://discuss.airbyte.io/t/90) [^2^]: [Documentation > Using-airbyte > Schema Change Management > Detect and Propagate Schema Changes connection setting](https://docs.airbyte.com/using-airbyte/schema-change-management#detect-and-propagate-schema-changes-connection-setting) [^3^]: [Forum Post: Custom source connector dynamic response > Answers](https://discuss.airbyte.io/t/897)