[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [GT] Trouble with backtest.pl and beancounter



RAS,

> -----Original Message-----
> From: Robert A. Schmied [mailto:ras
AT
acm.org]
> Sent: Wednesday, May 07, 2008 2:35 PM
> To: devel
AT
geniustrader.org
> Subject: Re: [GT] Trouble with backtest.pl and beancounter
> 
> > I think that lookup for additional data files or data sources should
> be
> > pushed into the data base module, so that we can avoid aborts or
give
> > better error messages.
> 
> i'm not sure what you mean by 'additional data files or data sources'?

What I meant was using data files/sources other than the standard file
with the market data, e.g., a per minute file, a weekly file, etc., all
for a single code.


> 
> from my simplistic view it would seem to me if a prices data access
> fails for a given $code one could attempt a name data access for that
> $code, if that access also fails it's rather likely that the database
> doesn't have support for that $code. (yes, i realize that it might
> have to be $code.$timeframe.$fileext)

Agreed. Would not be hard to do.

> 
> how to implement this across all supported databases is the challenge.
> most of the needed stuff exists (get_db_name) for the dbi apis, but
> are issues with the file based ones.
>