Thank you for your ideas, feedback and criticisms.
rb and Jeff
Future versions of Carte will not force you to list the column names
but will retrieve them from the database.
Jeff
The model macro produces a map which may then be merged with other
model maps so you could define the model in vario
Hi Brenton:
I think it would be nice if rather than specifying the columns of each
table in the call to the model macro, it was extracted from the
database directly.
Raph
On Jun 14, 6:14 pm, Brenton wrote:
> Hello group.
>
> I have been working on a relational mapping library for Clojure named
Using $, !, and $1 in the examples makes it a bit annoying to read,
especially if you just skip to the example queries to get a sense for
the library. It would be much clearer to make these something more
meaningful (e.g. lookup, query, update, find, get...)
It seems like your model macro is in f
On 14 June 2010 17:14, Brenton wrote:
> The current version is what I would consider to be a working prototype
> and I would love to get feedback from the community before I do much
> more work on this.
I've been thinking about a similar problem.
Most database mappers have three components:
1.
Very very nice!
On Jun 14, 11:14 am, Brenton wrote:
> Hello group.
>
> I have been working on a relational mapping library for Clojure named
> Carte.
>
> http://github.com/brentonashworth/carte
>
> The current version is what I would consider to be a working prototype
> and I would love to get f
Hi Brenton,
It's nice to see someone writing a relational mapper.
I never got farther than pondering on API design but I share my design
thoughts in case it can be useful to you:
* relations (tables/views/joins) would be a reference type (when
dereferenced they would return a seq or set of maps),
