logo

deltasql - Database Evolution under Control


Back to Website

Navigation Bar

Scripts

Modules

Projects

Branches/Tags

Synchronization

Statistics

Users

Utils

Help

deltasql Error Messages for 1.8.1

  • 1: The project name was not found (PROJECTNAME)
  • The project name used in the URL is not valid, it was specified as PROJECTNAME in the parameter project=. Instead, it has to be an identifier as specified under List Projects in the column name. This error can be issued only by deltasql clients, but not by using the synchronization form.

  • 2: The source branch was not found (BRANCHNAME)
  • The source branch name used in the URL is not valid, it was specified as BRANCHNAME in the parameter frombranch=. Instead, it has to be an identifier as specified under List Branches in the column name. This error can be issued only by deltasql clients, but not by using the synchronization form.

  • 3: The target branch was not found (BRANCHNAME)
  • The target branch name used in the URL is not valid, it was specified as BRANCHNAME in the parameter tobranch=. Instead, it has to be an identifier as specified under List Branches in the column name. This error can be issued only by deltasql clients, but not by using the synchronization form.

  • 5: The source branch BRANCHNAME does not belong to the project PROJECTNAME
  • The source BRANCHNAME as specified in the parameter frombranch= does not belong to the project specified in the parameter project=. Check the dependency here by using the columns name and project. This error can be issued only by deltasql clients, but not by using the synchronization form.

  • 6: The target branch BRANCHNAME does not belong to the project PROJECTNAME
  • The target BRANCHNAME as specified in the parameter frombranch= does not belong to the project specified in the parameter project=. Check the dependency here by using the columns name and project. This error can be issued only by deltasql clients, but not by using the synchronization form.

  • 8: -- no scripts to be executed (from BRANCH1 [VERSION1] to BRANCH2 [VERSION2])
  • This is not really an error. Deltasql found that there were no scripts needed to be executed. This message is just an SQL comment to inform that nothing needs to be done.

  • 9: Not possible to compute a dbsync update if version number is missing.
  • Deltasql server does not know the current version number. You probably forgot to specify it in the synchronization form or the deltasql client did not specify the version= parameter.

  • 10: Not possible to compute a dbsync update if project name is missing.
  • Deltasql server does not know the project name. You probably forgot to specify it in the synchronization form or the deltasql client did not specify the project= parameter.

  • 11: Project does not contain any modules. Please add at least one module to the project!
  • For the project you selected, no modules are defined. Please define first a module in Create module page. Add at list one script to this module in the Submit script page. Then add the newly defined module in List Projects page in this way: in the row where this project is listed choose the Add Module button. Only when you accomplished all these steps you can start synchronizing on this project.

  • 12: Version number has to be greater equal zero.
  • The version number has to be greater equal zero. Negative values are not a valid. Alphanumeric values are not valid as well.

  • 13: There is no path between target branch and source branch, please check them.
  • Deltasql starts from the target branch (the leaf of the tree) and goes back recursively until it hits the source branch. If deltasql is not able to find the source branch, it means there is an error in your synchronization request as the two branches are not related to each other. Please check your source and target branch before executing the synchronization step.

    Additionally, deltasql can only upgrade database schemas, but is not able to go back to previous states to the schema, due to the incremental, not reversible nature of the SQL scripts. This error could also mean that you mistyped the version number in the synchronization form, or that you chose a target branch which was done before the current one.

  • 15: The given version number is lower than when the branch was created.
  • There has to be a mistake in the version number you retrieved from the database schema as it is lower than when the branch was created. Or did you by chance specify the wrong source branch?

  • 16: Version number not allowed if synchronizing from a tag
  • You are not allowed to specify the version number in the synchronization form, as you are synchronizing from a tag. In fact, the tag implicitly sets a version number from where to start the synchronization... simply leave the version number blank in the synchronization form and try again :-)

  • 17: The tag [TAGNAME] does not belong to the project!
  • The source or target tag you specified does not belong to the project you would like to synchronize. Please check it!

  • 18: Database type not specified!
  • The database type for this project is not specified. Please go to List Projects, edit the project and choose a database type.