new queries and other minor changes

trade.sql: added column for allocation because it is necessary in the
process of calculating portfolio info. i commited these changes to the
db modify commands in the sqlplus prompt (did not need to remake_all).
insert_ind_ref: populates indicator reference info. *could not get the
date formatting to work
mva_mod.sql and query_mva.py: small modification to string formatting
because original one wasnt working for me
triggers: deleted, unnecessary
x_over.sql and x_under.sql: only changed the select criteria
load_finance.py: didn't want to delete your code but changed input for
mva columna to null so we can use the more efficient query_mva.py to
populate them in the db
populate_trades.py: did not delete, just added to .gitignore until i
have completed it
pop_temp_b_x_over.sql and similar: this will create trades for all
triggered buy orders if the buy triggers are triggered by 10 day mva
crossing over 25 day mva and vice versa for sells.  note the seq_tid
object i have created within oracle which auto-generates unique keys
set_rdp_relation: takes in strategy_id and 'B' or 'S' and populates
raw_data_parsing relation. must run after indicator reference is
populated. also as it currently stands, should only run for both
ind_ref objects if they have different action securities.
remake_all.sql: accidentally got deleted during last commit
see detailed summary

.gitignore: added unnecessary files
trade.sql: addition of column was necessary. made changes manually in
sqlplus script so i didn't need to run remake_all
insert_ind_ref: populates indicator reference relation. **does not
currently work because of date formatting.
mva_mod and query_mva: small string formatting changes because the
original setup was not working
x_over.sql and x_under.sql: only changed the "select" portion of the
query
load_finance.py: did not delete or comment out the portion which
calculates mvas, but set them to null because it is more efficient to
use mva_mod and query_mva to calculate/populate in sql
pop_temp_b_x_over: this will create trades when buys an indicator
reference has a buy triggered by the 10 day mva crossing over 25 and
vice versa for the similar file. it also auto-generates a trade_id
using a sql object called seq_tid that i have created in the db.
set_rdp_relation: this associates the strategy with the proper
securities and time periods by creating raw_data_parsing relationships.
it is a necessary step after the indicator criteria and query_data has
been filled.  the first argument is the strategy_id and second is 'B'
or 'S'.  It should be run twice only if the strategy contains a set if
indicator references where the buy and sell references have different
action_securities.
remake_all: this was only to replace my mistaken deletion