In the Readme, you mention the type issue is less relevant to sqlite-simple than the others.<br><br>Now, I've not actually used SQLite myself, but I have done some reading about it. I do understand that values of any type can be stored at any time in any column (except for the primary key, IIRC), but what happens to the declared type of a column when you create a table? Is that completely ignored? Can it be retrieved? Is it also returned somehow with the results?<br>
<br>I mean, it may still be a good idea to be able to check that somehow. Though this does add the complication that you still want to be able to use sqlite-simple with existing databases that don't necessarily follow the typing rules.<br>
<br>Best,<br>Leon<br><br><br><br><div class="gmail_quote">On Sat, Aug 11, 2012 at 2:39 PM, Janne Hellsten <span dir="ltr"><<a href="mailto:jjhellst@gmail.com" target="_blank">jjhellst@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi again!<br>
<br>
I finally found some time to work on the below idea of creating a<br>
sqlite-simple package that's modeled after postgresql-simple &<br>
mysql-simple.<br>
<br>
A working prototype can be found here: <a href="https://github.com/nurpax/sqlite-simple" target="_blank">https://github.com/nurpax/sqlite-simple</a><br>
<br>
I still need to do a bit of work on it to clean things up and add a<br>
bit more functionality. In particular, FromField instances are<br>
currently limited to only Ints and Strings - this is obviously not<br>
adequate for real use.<br>
<br>
I consider this to be ready for first release on hackage once I've<br>
done some more testing and closed the issues on<br>
<a href="https://github.com/nurpax/sqlite-simple/issues?milestone=1&state=open" target="_blank">https://github.com/nurpax/sqlite-simple/issues?milestone=1&state=open</a><br>
- but of course I may have missed something obvious.<br>
<br>
Comments, concerns? Let me know!<br>
<br>
Cheers,<br>
<br>
Janne<br>
<br>
On Wed, Aug 1, 2012 at 9:41 PM, Janne Hellsten <<a href="mailto:jjhellst@gmail.com">jjhellst@gmail.com</a>> wrote:<br>
> Hi list,<br>
><br>
> I've been looking for better Haskell sqlite bindings for few months now.<br>
><br>
> So far I've tried or investigated the following sqlite packages:<br>
><br>
> - hdbc-sqlite3<br>
> - sqlite<br>
> - direct-sqlite<br>
><br>
> At the same time I've played around a bit with postgresql-simple.<br>
> I've come to quite like the postgresql-simple API and would like to<br>
> have a access API for sqlite.<br>
><br>
> Unfortunately, all the existing sqlite bindings seem to offer a much<br>
> lower level interface.<br>
><br>
> I'm thinking that if no *-simple style Haskell library exists for<br>
> sqlite3, I'd like to create one.<br>
><br>
> I've exchanged a few e-mails about this with Leon and with his help<br>
> have a few ideas on how to go about it.<br>
><br>
> Leon suggested that the design should be two libraries: one low-level<br>
> library that can be unsafe to use directly and another medium-level<br>
> package that's built on the low-level library. The medium part would<br>
> borrow pretty directly from existing *-simple packages.<br>
><br>
> I dabbled a bit with my own low-level sqlite bindings but later came<br>
> to realize that the direct-sqlite package<br>
> (<a href="http://ireneknapp.com/software/" target="_blank">http://ireneknapp.com/software/</a>) seems to be pretty close to what I'd<br>
> need. So I'm thinking that could be the low-level part of<br>
> sqlite-simple.<br>
><br>
> Does this seem like a useful thing to build? (I know I'd need it.)<br>
><br>
> Does something like this already exist?<br>
><br>
> Thanks!<br>
><br>
> Janne<br>
<br>
_______________________________________________<br>
database-devel mailing list<br>
<a href="mailto:database-devel@haskell.org">database-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/database-devel" target="_blank">http://www.haskell.org/mailman/listinfo/database-devel</a><br>
</blockquote></div><br>