Allow specifying exactly what type of database string is expected in the database section for trace configuration

[Noremos]

The new syntax:

database = name /var/primary-db.fdb  
{  
enabled = true  
log_errors = true  
}  

database = name /var/secondary.fdb  
{  
enabled = true  
log_connections = true  
}  

database = regex (%[\\/](e[[:DIGIT:]]{{2}}).fdb)  
{  
enabled = true  
}  

# Default behavior for backward compatibility  
database = %[\\/]my_database.fdb  
{  
enabled = true  
}  

I chose database = name path.fdb over database name = path.fdb because it is easier to implement and parse, but it doesn't look as great, so it can be reimplemented.

[hvlad]

Please, avoid massive not related changes such as end space trimming.
It makes harder to read the patch looking for valuable changes.

[hvlad]

I chose database = name path.fdb over database name = path.fdb because it is easier to implement and parse, but it doesn't look as great, so it can be reimplemented.

Consider databaseName = path or databaseByName = path.

Note, in proposed syntax database name path.fdb also accepted, as = is not required by config code.

Also, your sample is wrong as default section must be the first one.

[Noremos]

Please, avoid massive not related changes such as end space trimming. It makes harder to read the patch looking for valuable changes.

Sorry, my IDE automatically trimmed the spaces and didn't display them in the DIFF editor

[Noremos]

I chose database = name path.fdb over database name = path.fdb because it is easier to implement and parse, but it doesn't look as great, so it can be reimplemented.

Consider databaseName = path or databaseByName = path.

Now databaseName and databaseRegex are used

database
{
	enabled = false
}

databaseName = /var/primary-db.fdb
{
	enabled = true
	log_errors = true
}

databaseRegex = (%[\\/](e[[:DIGIT:]]{{2}}).fdb)
{
	enabled = true
}

database = employee
{
	enabled = true
}