Overview
Korra is a library for introspection of maven packages. The library
provides mappings between different representations of the same jvm concept.
- maven coordinate and the jar file
- a 'resource' and its related jar and jar entry under a given context
- the resource can be:
I'll also mention that when I used to do C# and SQL I often found myself
often resorting to stored procs for high performance queries. Depending on
your SQL DB, you can often put quite a bit of conditional logic into the
queries, as long as that logic isn't executed row-by-row. Depending on how
adv
Sean Corfield has a great example of writing a log4j logging backend in
clojure:
http://corfield.org/blog/post.cfm/real-world-clojure-logging
On Tue, Jul 22, 2014 at 6:17 PM, Brian Craft wrote:
> Is there any good way to use timbre in a project with java libs, e.g.
> c3p0, that use java log
I forgot to include in the snippet, that I would do something like
(def live-repl-client (cljs.repl/channel-repl repl-env))
When you say channel-repl/cider-function, do you mean user/live-repl-client?
I don't quite understand what you mean by (prefix).
What I want is just to be able to evaluate
You'll want to read this thread:
https://groups.google.com/forum/#!topic/clojurescript/DHJvcGey8Sc
In particular:
"So if you have code that's like this, those components will want to clean up
after themselves in IWillUnmount."
That should address your first problem?
I'm not sure what to sugge
You could just add tests for extra params in OR clauses.
For example, instead of:
(str "SELECT ... main query stuff WHERE basic conditions"
> (when date-range (str " AND dateUpdated >= ? AND dateUpdated < ?"))
> (when qualifier " AND someColumn = ?"))
>
You do this:
SELECT ... main query stuff
Ditto here. We use honeysql because we need to manipulate and parse SQL
statements as part of a library for managing remote browser views.
On Wednesday, July 23, 2014 7:56:45 AM UTC-4, Colin Yates wrote:
>
> Another very satisfied honeysql user here. It matches this use case
> perfectly.
>
> On
Many of us started out in non-development jobs and worked our way into full
time coding. Tech support jobs are ok but I would focus more on QA jobs.
This might allow you to do some automated testing using
clojure/clojurescript and given that test code isn't given the scrutiny
that dev code goes
I've encountered two subtle but serious problems using om with core.async.
The first one is illustrated by this code:
https://github.com/akhudek/om-async-error
First, one obvious solution here is to move the dump-chan inside the form
state.
However, it's written this way to illustrate the err
Hi,
I just released friendui 0.3.3.
I added two callback functions where one can add additional logic after a
successful signup|activation. It's fairly easy to add more, so, if the need
for this exists, just add an issue to github.
I also added two more projects: https://github.com/sveri/frien
Hi All,
it's my pleasure to announce a new version of Gorilla REPL, v0.3.1. The
focus of this release has been usability and taking off some of the rough
edges. This version is now much friendlier to those: who like to use the
mouse; who have short screens; who hate multi-press keyboard shortc
We plan to launch a new school this year. We want to work with a firm that
is very progressive and has a lot of experience. Most importantly, we want
a firm that has lots of experience working and maintaining a university or
college website. Also, we want to have our site built with Clojure
p
Yes, we're using HoneySQL extensively at World Singles for our more complex
reporting queries - which was why I asked what Yesql users were doing to handle
conditionally built queries.
I really like the look of Yesql - and I can see the benefits for some of our
more straightforward queries so I
So as an update to this for anybody who's interested, I now have a working
version with no verification errors simply by moving the monitor-enter
outside the try block, so that if monitor-enter fails to acquire the lock,
monitor-exit is not called.
(the reason this wasn't working before was that I
IMO this is good programming practice.
If there exists a reasonable contract to check your argument/return value,
then use it.
You mentioned protocols; if an argument extends a protocol, use {:pre
[(satisfies? P a)]}
to check your argument.
The payoff is localised error messages. Clojure is type
Hi Wes,
I'd be on the "don't do that" side of the fence. I did something similar when I
first moved from Java to a dynamically typed language (I suspect that most
people do) and it hinders at least as much as it helps.
For me, the thing that I needed to internalise is that Clojure isn't lacking
Hello folks,
My question is, "Is it 'idiomatic' to perform type checking of function
arguments in :pre conditions"?
Coming to clojure from 15 or so years of Java development has been
something of a revelation to me, but I am worried that I am still
struggling a bit with some old habits, one o
In my project.clj I include two jar files:
:resource-paths ["resources/exterior_jars/forssj-optimization.jar"
"resources/exterior_jars/umontreal-ssj-2.5.jar"]
In my main.clj I import some objects from these dependencies:
(ns myproject.main
(:import [umontreal.iro.lecuyer.probdist ChiSquareDis
I'm compiling clojure on android and running it using the new ART runtime,
and all works fine apart from the locking macro which fails ART's bytecode
verification.
Example generated bytecode here:
https://gist.github.com/AdamClements/2ae6c4919964b71eb470
The try block in java doesn't cover the mo
Another very satisfied honeysql user here. It matches this use case
perfectly.
On Wednesday, 23 July 2014 10:15:09 UTC+1, David Powell wrote:
>
> I'm using honeysql for constructing dynamic queries (eg conditionally
> adding complex clauses). It feels a bit more composable to me, and seemed
>
For the record, I never ran in any structural issue when working with
clojure.java.jdbc and clojure.java.jdbc.sql. It lets you write clean and
composable queries and removes takes care of the essential (escaping and
the like).
On Wed, Jul 23, 2014 at 11:14 AM, David Powell
wrote:
> I'm using
I'm using honeysql for constructing dynamic queries (eg conditionally
adding complex clauses). It feels a bit more composable to me, and seemed
much easier to add the OR of several clauses to a query etc.
On Tue, Jul 22, 2014 at 1:28 PM, Michael Klishin <
michael.s.klis...@gmail.com> wrote:
>
Sean, that was exactly what we did when we changed to yesql. With separated
queries our Postgres specialist could optimize each query separately, and
for the if nesting we used cond or core.match. Even with all the
boilerplate of maintaining separated queries it was still much better than
Korma
23 matches
Mail list logo
