Issue 7 in orapig: automate creation of sample packages/modules
codesite...@google.com
http://code.google.com/p/orapig/issues/detail?id=7
New issue report by marhar:
- Ability to install all of the sample packages/tables with a single command.
- Ability to create all the demo modules (alltypes.py, keyword.py,
and tiny.py) from a single command.
Issue attributes:
Status: Accepted
Owner: MarkRoddy
Labels: Type-Enhancement Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
http://code.google.com/p/orapig/issues/detail?id=7
Comment #1 by marhar:
Can we assume having sqlplus? then we can just have a .sql
file. Or (thinking aloud), maybe we could make it self-contained
in orapig, and have an orapig --create-demos option?
My tiny unix brain gravitates towards Makefiles, but maybe
there's a pythonic way that will work for our windows breathren
as well?
codesite...@google.com
http://code.google.com/p/orapig/issues/detail?id=7
Comment #2 by MarkRoddy:
For installing the sample packages I was planning on adding a makefile
target along
the lines of:
install-samples: alltypes.sql keyword.sql tiny.sql
sqlplus $(CONNSTR) @alltypes.sql
sqlplus $(CONNSTR) @keyword.sql
sqlplus $(CONNSTR) @tiny.sql
I personally perfer using makefiles to define multistep operations
especially when
the have tight dependencies between eachother. For instance, making the 'export'
step a dependency of the test step, so if someone types 'make test' and hasn't
generated the python code the makefile will reconize and perform this step.
Also, since this would only affect those users that want to run the
tests, I don't
think its that big of a requirement that they have access to Make.
Most of my
Python projects at work are on Windows, and the majority of them use
makefiles to
define import operations. I can't say that this is necessarily the
norm, but it
works quite well in my experience.
codesite...@google.com
http://code.google.com/p/orapig/issues/detail?id=7
Comment #3 by MarkRoddy:
Patch to the testing Makefile that has commands for installing sample packages,
generating python wrappers for sample packages, and dropping sample
packages. I
also added an sql script to uninstall the samples. Not sure how
everyone else feels
about a 'need' for such a script. It was a bit of a pain to test the
installing the
samples without the ability to uninstall them. Plus it would be nice
for those that
are curious and install the samples to be able to uninstall them.
Attachments:
Makefile.patch 1.2 KB
uninstall.sql 139 bytes