开云体育

Hello,

Only go as complex as you need to. CSV files are quick and easy to examine. If you implement the interface to the data-getting functionality as a class, you can always swap it out for another implementation if you wish to enhance it later.

My live DB for trading is around 60gb, and it's not because I harvested a lot of tick data. But it started small enough to run from CSV files.

So plan for the fact your requirements will change.

Best wishes,

M

On Tue, 27 Oct 2020 at 20:01, Jens Rohweder <twsapigroup@...> wrote:

Dear Hedgemoney,

we are using MariaDB for large?dataset. However, storing the data into SQL and retrieving it back is more complicated?than using csv-files or Google Drive.

I prefer storing the data in csv-files. Python offers so many tools and very efficient methods to calculate all kind of models or output. And you may visualize the output with Dash (plotly).?

Best regards

Jens

Am Di., 27. Okt. 2020 um 20:47?Uhr schrieb <hedgedmoney@...>:

hi

I didn't see any post that asked this directly so, I'll ask it.

I'm trying to get time/sales of options data end of day(EOD)?
will use tws api and python.
I think i should organize the data in a db rather than file, excel....
I may build a front end webpage to view the data?

so which one:
leaning SQLite
i hear mySQL is popular as is PostGreSql

My thought is to use SQLite and migrate to the other if I'll need it....
Any comments and opinions would be appreciated....

Thanks

--

+44 (0) 7528 551604?
Gulfstream Software - Winner Risk Management Awards 2010
This message is subject to :