Hi,
I don't not want to blindly load/print *everything* but I do want
swiftly query *anything*, which is usual in exploratory computing,
especially in the first phases. That's where a proper interface between
Pharo and SQLite is needed and I would like to help in having it, at
least reporting the issues on Pharo 4 and now on Pharo 5. Meanwhile I
will query and export results to csv files, which is suboptimal, but
lets me advance while I have more clues about what's now working or I'm
not doing well.
Cheers,
Offray
On 13/04/16 01:09, stepharo wrote:
but you can have your objects in memory and you do not have to blindly
print everything or put everything in a table.
with moose sometimes we have 600K objects in an array.
I think that we need more clever stream to filter what we want to load.
Le 13/4/16 02:49, Offray Vladimir Luna Cárdenas a écrit :
Hi,
On 12/04/16 16:51, Stephan Eggermont wrote:
On 12/04/16 22:44, Offray Vladimir Luna Cárdenas wrote:
I'm working with visualizations a external dataset which contains 270k
records. So the best strategy seems to bridge pharo with SQLite to
keep
requirements low while using Roassal to visualize aggregated
information
that is obtained from querying the database.
It won't fit in image?
I tried with RTTabTable and NeoCVS but they can not load the data. I
made a test drawing 150k points and the image starts to lag and
trying to query the data becomes inefficient compared to query the
data on SQLite. For the moment I'll export the query results to CVS,
but I'll hope to have the SQLite bridge working soon.
Offray
