Ruby-style migrations are great but, as others have said, they lend
themselves better to another layer of abstraction. I was thinking of a
lower-level alternative to migration. We could find a way to construct
an ast from the current database schema and then compare it with the
one generated by the
I've implemented Migrations in Conjure. They don't use ClojureQL, but
it might be a good place to start (steal code). After looking over
ClojureQL, I'm definitely interested in pulling it into Conjure in a
future release.
-Matt
--
You received this message because you are subscribed to the Googl
On Dec 14, 2:23 pm, Stuart Halloway wrote:
> Migrations would be awesome. As to where they should go, I am of two
> minds. They are clearly a separate layer, and could be a separate
> project that relied on ClojureQL. OTOH, we use migrations on 100% of
> our projects that use relational da
Migrations would be awesome. As to where they should go, I am of two
minds. They are clearly a separate layer, and could be a separate
project that relied on ClojureQL. OTOH, we use migrations on 100% of
our projects that use relational data, so why bother with an
additional dependency?
By
> I'm fully aware that my argumentation would carry much more weight if
> I had the opportunity to contribute some code for migrations, but I
> currently don't have :(
Your argument lacks no weight. You make a good case for migrations so
I'll look into it, and I'll be very happy to write up the fi
On Dec 14, 12:17 pm, LauJensen wrote:
> > It's really been a time saver and I think it's a really good fit with
> > ClojureQL.
>
> > Raphaël
>
> Raphaél, thank you for bringing this to my attention, it looks
> interesting.
>
> I think this falls more in the tool-category than the language-
> cat
>
> It's really been a time saver and I think it's a really good fit with
> ClojureQL.
>
> Raphaël
Raphaél, thank you for bringing this to my attention, it looks
interesting.
I think this falls more in the tool-category than the language-
category. In its simplest form ClojureQL aims to make you
> > And a suggestion: having migrations in CQL would be great!
>
> Could you elaborate a little?
Migrations are a way to manage the evolution of a schema of a
database. I'm familiar with migration in Ruby on Rails which are
explained here: http://api.rubyonrails.org/classes/ActiveRecord/Migration.
> I'm wondering: how would you compare the use of ClojureQL and clj-
> record(which sadly doesn't show much activity currently)? Isn't CQL
> going back to the SQL level or database queries, whereas clj-record is
> at a higher level? Would it be easy to code this higher level layer on
> top of cql?
On Dec 11, 11:58 am, LauJensen wrote:
> Hi all,
>
> ClojureQL is now moved to Gradle and Jars are pushed to Clojars as
> version 0.9.7
>
> Blogpost on
> status:http://www.bestinclass.dk/index.php/2009/12/clojureql-where-are-we-go...
Very interesting.
I wondered some days ago what is the best way
10 matches
Mail list logo
