gudusoft.gsqlparser.sqlenv

Class IdentifierProfile.Builder

Object

gudusoft.gsqlparser.sqlenv.IdentifierProfile.Builder

Enclosing class:

IdentifierProfile

public static final class IdentifierProfile.Builder
extends Object

Builder for creating customized IdentifierProfile instances.

The builder is seeded from vendor defaults. Overrides can be applied per object group. The built profile is immutable.

Usage example:

 IdentifierProfile profile = IdentifierProfile
     .builder(EDbVendor.dbvmssql)
     .withColumnRules(customColumnRules)
     .build();
 

Method Summary

Modifier and Type	Method and Description
IdentifierProfile	build() Build an immutable IdentifierProfile.
IdentifierProfile.Builder	withColumnRules(IdentifierRules rules) Convenience: override COLUMN_GROUP rules.
IdentifierProfile.Builder	withFlags(IdentifierProfile.VendorFlags flags) Override VendorFlags (replaces default-seeded flags).
IdentifierProfile.Builder	withNameRules(IdentifierRules rules) Convenience: override NAME_GROUP rules.
IdentifierProfile.Builder	withObjectRules(ESQLDataObjectType objectType, IdentifierRules rules) Override the rules of ONE object category — catalog/project, schema, table, column, function … — independently of every other category (design §5.1).
IdentifierProfile.Builder	withoutObjectRules(ESQLDataObjectType objectType) Drop a category override set earlier, so the category inherits its group / vendor rule again.
IdentifierProfile.Builder	withoutRules(IdentifierProfile.ObjectGroup group) Drop a group override set earlier, so the group falls back to the vendor-seeded rule.
IdentifierProfile.Builder	withRoutineRules(IdentifierRules rules) Convenience: override ROUTINE_GROUP rules.
IdentifierProfile.Builder	withRules(IdentifierProfile.ObjectGroup group, IdentifierRules rules) Override the rules for a specific object group.

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

withFlags

public IdentifierProfile.Builder withFlags(IdentifierProfile.VendorFlags flags)

Override VendorFlags (replaces default-seeded flags). Re-seeds rules that depend on flags while preserving explicit overrides set via withRules().

Parameters:

flags - new vendor flags

Returns:

this builder

withRules

public IdentifierProfile.Builder withRules(IdentifierProfile.ObjectGroup group,
                                           IdentifierRules rules)

Override the rules for a specific object group.

Parameters:

group - the object group to override

rules - the custom rules

Returns:

this builder

withNameRules

public IdentifierProfile.Builder withNameRules(IdentifierRules rules)

Convenience: override NAME_GROUP rules.

Parameters:

rules - the custom rules for names

Returns:

this builder

withColumnRules

public IdentifierProfile.Builder withColumnRules(IdentifierRules rules)

Convenience: override COLUMN_GROUP rules.

Parameters:

rules - the custom rules for columns

Returns:

this builder

withRoutineRules

public IdentifierProfile.Builder withRoutineRules(IdentifierRules rules)

Convenience: override ROUTINE_GROUP rules.

Parameters:

rules - the custom rules for routines

Returns:

this builder

withObjectRules

public IdentifierProfile.Builder withObjectRules(ESQLDataObjectType objectType,
                                                 IdentifierRules rules)

Override the rules of ONE object category — catalog/project, schema, table, column, function … — independently of every other category (design §5.1).

This is the finest granularity and wins over a group override and over the vendor default. It is deliberately a new name rather than an overload of withRules: withRules(null, rules) would become ambiguous, and an object CATEGORY is not an object group.

The argument is a category, never the name of a particular dataset, table or column — a profile expresses "how table names compare here", not "this table compares like that".

Repeating a category keeps the LAST value. To go back to inheriting, call withoutObjectRules(ESQLDataObjectType); null rules are rejected rather than treated as some implicit rule.

Note what a category override does and does not claim: it is the analysis assumption the CALLER supplies. It is not read from a live server, and an arbitrary override is not automatically a vendor's native semantics.

Parameters:

objectType - the object category to configure

rules - the complete rule cell (unquoted fold/compare, quoted fold/compare)

Returns:

this builder

withoutObjectRules

public IdentifierProfile.Builder withoutObjectRules(ESQLDataObjectType objectType)

Drop a category override set earlier, so the category inherits its group / vendor rule again. A category that was never overridden is unaffected.

Parameters:

objectType - the object category to stop overriding

Returns:

this builder

withoutRules

public IdentifierProfile.Builder withoutRules(IdentifierProfile.ObjectGroup group)

Drop a group override set earlier, so the group falls back to the vendor-seeded rule. Category overrides are untouched — they sit above the group level.

Parameters:

group - the object group to stop overriding

Returns:

this builder

build

public IdentifierProfile build()

Build an immutable IdentifierProfile. Merges seeded rules with overrides (overrides win), then applies per-category overrides.

Returns:

the built profile