Etendo Database Synchronizer FAQs

Question 1

What is the primary function of the /etendo:update command?

Accepted Answer

The command triggers the update.database Gradle task which applies changes from the Etendo Application Dictionary (XML sourcedata) and module definitions directly into the live PostgreSQL database.

Question 2

Can I run the update process faster for large databases?

Accepted Answer

Yes, the skill supports a threads=N argument which enables parallel execution, significantly reducing the time required for schema updates in large environments.

Question 3

How does the skill handle database connection issues?

Accepted Answer

Before running the update, the skill checks if the database is reachable via Docker filters or psql commands and provides specific instructions to start the service if it is offline.

Question 4

Is a build required after running the update?

Accepted Answer

Typically yes. If arguments like 'full' are used, or if columns were added, the skill guides you to run a smartbuild or generate.entities to ensure the Java model matches the new database schema.

Question 5

What happens if a column size change is rejected during the update?

Accepted Answer

The skill identifies the specific table and column causing the conflict and provides the necessary SQL ALTER TABLE command to manually fix the size before re-running the synchronization.

Etendo Database Synchronizer

주요 기능

사용 사례

Etendo Database Synchronizer

주요 기능

사용 사례