marmolubio + sql 91
Call for GSoC: bring Haskell to the masses
february 2012 by marmolubio
Looking at Hibernate, you can practically see a list of ways to fail at "wrapping" SQL: you can ignore the diversity of databases, you can ignore the power of SQL queries, you can try to reimplement SQL poorly, you can try to implement your own API for building SQL.
haskell
sql
february 2012 by marmolubio
datetime - Daylight saving time and Timezone best practices - Stack Overflow
november 2011 by marmolubio
You need to know about the Olson database, which is available from ftp://elsie.nci.nih.gov/pub. It is updated multiple times per year to deal with the often last-minute changes in when (and whether) to switch between winter and summer (standard and daylight saving) time in different countries around the world.
sql
stackoverflow
november 2011 by marmolubio
Are there any e-commerce websites that use NoSQL databases - Stack Overflow
october 2011 by marmolubio
The real question, IMO, is whether you can live with the restrictions that a NoSQL database puts on you - in particular, the general lack of ad-hoc queries.
nosql
sql
october 2011 by marmolubio
A Simple Guide to Five Normal Forms in Relational Database Theory
october 2011 by marmolubio
The normalization rules are designed to prevent update anomalies and data inconsistencies. With respect to performance tradeoffs, these guidelines are biased toward the assumption that all non-key fields will be updated frequently. They tend to penalize retrieval, since data which may have been retrievable from one record in an unnormalized design may have to be retrieved from several records in the normalized form.
sql
reference
october 2011 by marmolubio
www.dbdebunk.com/quotes2006.html
october 2011 by marmolubio
deirdre: Any of Joe Selko's [sic] SQL for Smarties stuff (including any of his several books) is worth reading. Oh, you mean like only using 15 tables when a "true" relational design would have 35 tables and each query/insert has 10 more joins? Sure. Usually, there's a point where being more "relational" doesn't make business sense in the terms of how much hardware / developer time you need to throw at it to be pure "relational."
sql
october 2011 by marmolubio
mysql - When to use MongoDB or other document oriented database systems? - Stack Overflow
october 2011 by marmolubio
What am I going to build my next app on? Probably Postgres. Will I use NoSQL? Maybe. I might also use Hadoop and Hive. I might keep everything in flat files. Maybe I’ll start hacking on Maglev. I’ll use whatever is best for the job. If I need reporting, I won’t be using any NoSQL.
nosql
sql
october 2011 by marmolubio
Amazon.com: Inside ODBC (Microsoft programming series) (9781556158155): Kyle Geiger: Books
october 2010 by marmolubio
Whatever API you use for database access -- be it ODBC, or DbLib, or embedded SQL, or OLE DB ('objectified' version of ODBC really)
sql
shopping
october 2010 by marmolubio
David Coldrick's Weblog: New Version of H2 Database Released
july 2010 by marmolubio
There are other cases where Derby performs better than H2 or HSQLDB
sql
july 2010 by marmolubio
Copy this bookmark: