Hi Max,
thanks for that hint. I had tried IxSet by itself and was unaware that
Happs-state might be a solution.
Performance *is* a problem, not time but space. If you meant a time
performance problem, that'd be acceptable, the app with SQLite is running
too fast as it is. But the machines this app is supposed to be able to run
are Win2k machines, so a space performance problem *is* a problem.
Which one did you mean?
Günther
Am 06.08.2009, 07:19 Uhr, schrieb Max Desyatov
<[email protected]>:
As I can say from my experience of usage of hdbc-sqlite3 and
happstack-state, the latter covers everything you ever wanted from
sqlite3 and more. It you aren't too concerned about performance, you
can free yourself from many tedious routines that are imminent when you
work with relational database. Elaborated data model design coupled
with some generics technique (uniplate with derive, e.g.) gives you a
possibility to write down your domain problem directly to haskell.
CK Kashyap <[email protected]> writes:
I'd be very interested to see a rdbms implementation in Haskell ...
perhaps a port of sqlite
Regards,
Kashyap
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe
