bytebase/bytebase · error

no object name is specified

Error message

no object name is specified

What it means

Thrown by tsqlIsFieldSensitive when all four normalized name components (database, schema, table, column) are empty, so the resulting mask is maskNone. There is nothing to resolve: the function requires at least one qualifier level (in practice a column name) to identify a field for sensitivity analysis.

Source

Thrown at backend/plugin/parser/tsql/query_span_extractor.go:310

			return base.QuerySpanResult{}, errors.Errorf(`table name %s is specified without column name`, normalizedTableName)
		}
		mask |= maskTableName
	}
	if normalizedSchemaName != "" {
		if mask&maskTableName == 0 {
			return base.QuerySpanResult{}, errors.Errorf(`schema name %s is specified without table name`, normalizedSchemaName)
		}
		mask |= maskSchemaName
	}
	if normalizedDatabaseName != "" {
		if mask&maskSchemaName == 0 {
			return base.QuerySpanResult{}, errors.Errorf(`database name %s is specified without schema name`, normalizedDatabaseName)
		}
		mask |= maskDatabaseName
	}

	if mask == maskNone {
		return base.QuerySpanResult{}, errors.Errorf(`no object name is specified`)
	}

	// We just need to iterate through the fromFieldList sequentially until we find the first matching object.
	//
	// It is safe if there are two or more objects in the fromFieldList have the same column name, because the executor
	// will throw a compilation error if the column name is ambiguous.
	// For example, there are two tables T1 and T2, and both of them have a column named "C1". The following query will throw
	// a compilation error:
	//   SELECT C1 FROM T1, T2;
	// Users can specify the table name to disambiguate:
	//   SELECT T1.C1 FROM T1, T2;
	// If an alias is set the original table name is shadowed:
	//   SELECT T1.C1 FROM T1 AS T3, T2;  -- invalid
	for _, tableSource := range q.tableSourcesFrom {
		if mask&maskDatabaseName != 0 && !q.isIdentifierEqual(normalizedDatabaseName, tableSource.GetDatabaseName()) {
			continue
		}
		if mask&maskSchemaName != 0 && !q.isIdentifierEqual(normalizedSchemaName, tableSource.GetSchemaName()) {

View on GitHub (pinned to 1870550677)

Solutions

1. Check the expression node before calling: only invoke tsqlIsFieldSensitive for actual column references with a non-empty column name.
2. Fix the upstream parsing/normalization so identifiers are populated; log the node kind that produced an empty tuple.
3. Return an empty/unknown sensitivity result for non-identifier expressions instead of calling the resolver.

Example fix

// before: resolve regardless
result, err := q.tsqslIsFieldSensitive(db, schema, table, column)
// after: guard empty input
if column == "" {
    return base.QuerySpanResult{}, nil // not a column reference
}
result, err := q.tsqslIsFieldSensitive(db, schema, table, column)

if db == "" && schema == "" && table == "" && column == "" {
    return errors.New("empty object name for field resolution")
}

func hasAnyNamePart(db, schema, table, column string) bool {
    return db != "" || schema != "" || table != "" || column != ""
}

res, err := q.tsqslIsFieldSensitive(db, schema, table, column)
if err != nil && strings.Contains(err.Error(), "no object name is specified") {
    return base.QuerySpanResult{}, nil // not an identifier expression
}

When it happens

Trigger: resolveExpressionNode or collectPredicatesInScope invoking tsqlIsFieldSensitive with an entirely empty name tuple — e.g. an expression node with no identifier part, an empty column reference, or default-initialized name fields.

Common situations: Parser producing an empty identifier for expressions like `SELECT [] FROM t` or unhandled node kinds passed to the resolver; programmatic callers forgetting to set any name fields.

Understand the failure class

Background: "must not be empty", "cannot be empty" — required-field validation errors across open-source libraries — this error's family across 41 libraries.

Related errors

• no matching column %q.%q.%q.%q
• linked server is not supported yet, but found %q
• failed to extract view body
• table name %s is specified without column name
• database name %s is specified without schema name

AI-assisted analysis of bytebase/bytebase@1870550677 (2026-09-06). Data as JSON: /api/errors/b00306934a49d857. Report an issue: GitHub.