New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow non-SQL (un-)deployment scripts #1

Open
mlawren opened this Issue Apr 7, 2012 · 6 comments

Comments

Projects
None yet
4 participants
@mlawren
Copy link
Contributor

mlawren commented Apr 7, 2012

[I'm not sure where you are tracking issue or feature requests so for now here is as good as anywhere I guess]

It may be necessary to use scripts written in languages other than SQL (eg Perl) to perform certain steps when upgrading or downgrading a database. These scripts should also be part of the dependency graph, and of course indempotent. Database connection parameters could be passed in as environment variables or as yaml/json on stdin etc.

@theory

This comment has been minimized.

Copy link
Collaborator

theory commented Apr 7, 2012

This is as good a place as any. A good place, actually.

I have no plans myself to support anything other than SQL scripts, but I think it would be easy to do. The current spec calls for files to have any kind of extension, but maybe it should be limited to .sql. That way, we can always just specify that other extensions mean other kinds of scripts. So a .pl would be a Perl script and a .py would be a Python script.

Would you be interested in adding that support at the appropriate time, @mlawren?

@mlawren

This comment has been minimized.

Copy link
Contributor

mlawren commented Apr 7, 2012

Wow, github issues got email integration...

to have any kind of extension, but maybe it should be limited to
.sql. That way, we can always just specify that other extensions
mean other kinds of scripts. So a .pl would be a Perl script and a
.py would be a Python script.

Perhaps match anything not '.sql' with the execute bit set?

I have no plans myself to support anything other than SQL scripts,
but I think it would be easy to do. The current spec calls for files
...
Would you be interested in adding that support at the appropriate
time, @mlawren?

In principle yes, at least without knowing in advance my workload and
continued interest. I'm 'watching' your repo and it's dead easy to fork
at the appropriate time.

If sqitch works out well I can see myself rewriting a whole bunch of
SQL which might otherwise keep me busy... but that could only be a good
thing.

@theory

This comment has been minimized.

Copy link
Collaborator

theory commented Apr 11, 2012

Perhaps match anything not '.sql' with the execute bit set?

I don't think that'd be very friendly to Windows. I think just relying on extensions should do the trick.

In principle yes, at least without knowing in advance my workload and
continued interest. I'm 'watching' your repo and it's dead easy to fork
at the appropriate time.

Awesome, thanks. I hope to finish the tutorial today, and then start hacking.

—Theory

@rightfold

This comment has been minimized.

Copy link

rightfold commented Jun 23, 2015

@mlawren has any progress been made on this? If not then I don't mind picking it up.

@mlawren

This comment has been minimized.

Copy link
Contributor

mlawren commented Jun 23, 2015

@docteurklein

This comment has been minimized.

Copy link

docteurklein commented Jan 13, 2017

also see #323 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment