[ts-gen] (no subject)

Ugo Kanain ugokanain at newsguy.com
Wed Sep 26 23:02:10 EDT 2007


Though my requirements are rather simple, I found the shim to be a  
rather comprehensive solution to interact with IB's api, and probably  
the only viable solution to use a sql server. Would like to extend my  
appreciation for Bill's and Herrold's effort in putting out the shim  
for all to use. Also on their patience when dealing with newbies,  
while we try to learn to use the trading-shim.

While trying to use the shim, I found that the db is a complex and  
interrelated structure, which is not easily maintained. The manual  
recommends that you modify the sql files, and then reload the  
database. Since it requires changes to be carried onto several tables  
at the same time. So changes aren't a task easily carried out by hand.

Another layer of complexity and in order to save space, is the use of  
the numerical foreign keys in the records, so the resulting structure  
is not easily read by people. Notwithstanding that most of the  
database has already been setup by Bill, there are times one would  
like to make changes.

I was thinking of an easier solution that allows the modification of  
the db, through a view of the record. In such a view, all the related  
fields would be shown with more descriptive information (maybe Bill  
can put a link that shows one of the table views). Then all the other  
tables would be affected.

Have started playing with a web interface. However, can't decide what  
would be the best way to do things; top to bottom or bottom to top.  
Don't know if all tables allow both approaches, but imagine most should.

To illustrate the idea, suppose we are adding a stock to the  
database. Though the stock table has to be changed,  it also needs to  
modify the underlying and symbol tables:
1) Top to bottom: Modifying the Symbol table would cascade the  
changes down to  the Underlying and Stock tables

2) Bottom to Top: Modifying the Stock table would cascade the changes  
upwards unto the Underlying and Symbol tables.

Haven't played with the shim to know which approach would be a better  
solution. So would appreciate to know, first if there is any interest  
on this project (would require an apache server with php), and  
secondly your comments as to which approach to follow.




More information about the ts-general mailing list