Add in SQLCMD variables

paupino / psqlpack

A logical database management system for PostgreSQL enabling incremental database deployment.

Apache License 2.0

8 stars 2 forks source link

Add in SQLCMD variables #20

Open paupino opened 7 years ago

paupino commented 7 years ago

Command variables will allow in place variable matching to be applied to scripts on parse. This could be resolved entirely at the Lexer level. In saying that, we may want to have some better lexer Debug level logging before doing this i.e. start logging symbols, state change as well as symbol replacements (this task).

paupino commented 7 years ago

May rely on #11

paupino commented 6 years ago

I don't think the lexer stage is right here - although there will need to be Lexer changes made. The reason why is because the replacement variable may not be known until publish.

paupino commented 6 years ago

[ ] Include variable identification within lexer
[ ] Allow for reasonable variable replacement within parser
[ ] Add default parameters into project file
[ ] Add override parameters into publish profile
[ ] Add override parameters to command line
[ ] Add variable resolution table to Package as well as missing validation
[ ] Ensure variable replacement at runtime

paupino commented 6 years ago

Removing this from MVP since it isn't really a requirement. I'll put that in the next version milestone.