You're very welcome - and thanks to everybody who's tried it out!
Lau
Tim Robinson wrote:
Thank you for making this.
It's a great idea and really enjoyable to use.
Tim
On Jan 5, 7:14 am, LauJensen lau.jen...@bestinclass.dk wrote:
Hey everybody,
Just a quick heads up that ClojureQL
seancorfi...@gmail.com wrote:
On Thu, Jan 6, 2011 at 2:33 AM, LauJensen lau.jen...@bestinclass.dk wrote:
Yes the two statements are equivalent. ClojureQL compiles everything
to prepared
statements, with every argument automatically paramterized.
Cool, that's what I'd hoped. But just to clarify
, it should
hopefully generate what they would have written by hand.
Lau
On Jan 6, 4:23 am, Sean Corfield seancorfi...@gmail.com wrote:
On Wed, Jan 5, 2011 at 6:14 AM, LauJensen lau.jen...@bestinclass.dk wrote:
Just a quick heads up that ClojureQL 1.0.0 is now released. All
interfaces should
to include that dialect in CQL. Right now, I think
95% of the functions will actually run fine on Sqlite.
On Jan 6, 4:09 pm, faenvie fanny.aen...@gmx.de wrote:
On Jan 5, 3:14 pm, LauJensen lau.jen...@bestinclass.dk wrote:
... Works out of the box with PostgreSQL and MySQL ...
nice work !
your
Hey everybody,
Just a quick heads up that ClojureQL 1.0.0 is now released. All
interfaces should be final and there are no known bugs. Works out of
the box with PostgreSQL and MySQL but the compiler is a multimethod so
you can implement your own backend if you need to work with other
database
Is there a way to do this (or something similar) inClojureQLor is it
planned for a future version?
Janico
On Thu, Nov 25, 2010 at 7:27 PM, LauJensen lau.jen...@bestinclass.dk wrote:
There's some valuable food for thought in this thread.
My major problem with support various backends is the amount
only via strings
and not via a mechanism within ClojureQL allows its use in specific
applications but effectively prevents use for libraries and
frameworks. Indirect use of ClojureQL could yield unacceptable
performance with no elegant fix.
On Nov 24, 11:28 pm, LauJensen lau.jen
to write in SQL directly.
Thanks,
-Luke
On Nov 18, 2:10 pm, LauJensen lau.jen...@bestinclass.dk wrote:
Hi gents,
For those of you who have followed the development
of ClojureQL over the past 2.5 years you'll be excited
to know that ClojureQL is as of today being released
as 1.0.0 beta1
be better as a join on
another.
Thanks so much for the detailed answer...
-Luke
On Nov 24, 3:37 am, LauJensen lau.jen...@bestinclass.dk wrote:
Hi Luke,
Thanks!
Initially CQL0.1 was motivated by everything in Clojure which was
the driving design principle behind the first version
Hi Brenton,
Yes the OFFSET/LIMIT syntax differs from backend to backend. However
in some instances (like MySQL/PostgreSQL) they have ensured
compatability so that the same statement will run on several DBs
although the syntax might not be considered 'native'. For something
like Oracle there
@Mark: Thanks! :)
@Jeff: Thanks a lot. Link is fixed now.
@Sam: Thanks!
@James: Wow - I should put that in my resume, thanks a lot !
@Mark E:
Half right.
ClojureQL has a major focus on queries as they are the largest
part of our interaction with databases. However it piggy-backs
on
)
(( ? = ? ) OR ( ? ? ? ))
cql.predicates (:env *2)
[x 5 10 y 5]
I hope to release this very shortly as its the final building block
needed
for 1.0.0 FINAL - Injection protection.
Lau
On Nov 23, 4:57 pm, Wilson MacGyver wmacgy...@gmail.com wrote:
On Tue, Nov 23, 2010 at 5:34 AM, LauJensen lau.jen
Hi gents,
For those of you who have followed the development
of ClojureQL over the past 2.5 years you'll be excited
to know that ClojureQL is as of today being released
as 1.0.0 beta1.
That means that the significant primitives from Relational
Algebra are all in place and functional. The
Hi Todd,
I'll recommend you to open this up as a separate issue, seeing how
this thread is meant to specifically discuss changes in the 'equiv'
branch. Your examples makes sense, as a 2 item collection cannot open
up more than 2 threads, and a 20 item collection, will open n + 2
threads as
Konrad,
Im not following where this would be a problem in terms of
optimization. In the definition for map,
all that needs to be added is a check for a symbol? and the resulting
sequence could look and act
exactly like it would, had you manually added the #(.method %) right?
If the technical
To avoid confusion Im pasting from another thread:
Getting ready:
http://www.bestinclass.dk/index.php/2009/12/clojure-101-getting-cloju...
Doing simple pages:
http://www.bestinclass.dk/index.php/2009/12/beating-the-arc-challenge...
Including SQL:
Hey Markus,
Probably not what you want to hear, but I think great names are both
memorable and descriptive. Leaning on those criterias clj-native is
not bad at all.
Lau
On 17 Mar., 08:08, mac markus.gustavs...@gmail.com wrote:
After just a little more test and polish I plan on calling
Hi Lee,
Personally I think JSwat does the job right in that you can break the
code and get a look at local variables. There has also been release a
'debug-repl' which allows you to halt execution and jump into a REPL,
like so: http://georgejahad.com/clojure/debug-repl.html. There exists
2
Hi Ben,
I think we often get the impression that functional programming is
directly connected to monads, but in practical terms the important
concepts are pure functions and persistent immutable datastructures.
The learning curve when coming from an imperative language, lies (for
me at least)
Hey Tim,
Welcome - I might be restating, but this should get you going quickly:
Getting ready:
http://www.bestinclass.dk/index.php/2009/12/clojure-101-getting-clojure-slime-installed/
Doing simple pages:
http://www.bestinclass.dk/index.php/2009/12/beating-the-arc-challenge-in-clojure/
Eugen,
Fantastic insight - I cant wait to work that into a blogpost :)
Lau
On 17 Mar., 15:56, Eugen Dück eu...@dueck.org wrote:
All,
Developing in clojure is a lot of fun, at least it was for me and a
project of mine - except for one thing: Deploying the app as Java Web
Start app, that
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
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
On Dec 14, 2:23 pm, Stuart Halloway stuart.hallo...@gmail.com 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
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-going/
Thanks,
Lau
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To
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? Or
26 matches
Mail list logo
