Hi Joe,
Mapper does not work standalone, its not like ActiveRecord in that
sense - its tied to lift-webkit. Your best bet would be to go with
JPA; I think that will serve you better anyway.
Cheers, Tim
On Jun 23, 4:47 pm, Joe Wass j...@folktunefinder.com wrote:
Good afternoon (at least in
I used mapper in an offline (demo) app. You have to include the util and http
jars IIRC but it's a desktop app. If you're subcribed to scala-user, I posted
it (I think last week) in the thread about a scala SWT DSL.
-
Timothy Perretttimo...@getintheloop.eu
I've used Mapper in desktop apps too. It works fine.
--j
On Tue, Jun 23, 2009 at 9:56 AM, Naftoli Gugenhem naftoli...@gmail.comwrote:
I used mapper in an offline (demo) app. You have to include the util and
http jars IIRC but it's a desktop app. If you're subcribed to scala-user, I
posted
I didn¹t say that it *wouldn¹t* work, just that its tied to lift-webkit...
Besides, he says that he will be doing a lot of data intensive processing -
seems like JPA would play better there as Mapper is usually has a ceiling of
functionality and then it becomes necessary to move to JPA anyway.
The OP claims his data model is simple enough for Mapper.
If he doesn't mind adding the lift-webkit jar to his classpath, I don't see
a problem with using Mapper.
--j
On Tue, Jun 23, 2009 at 10:46 AM, Timothy Perrett
timo...@getintheloop.euwrote:
I didn¹t say that it *wouldn¹t* work, just
Thanks for all advice. The non-lift apps aren't particularly
complicated at the database end (they take stuff out, run some
algorithms and put stuff back), but I would need quick insertion. So
far I've done it with native SQL but would happily go ORM. I would
consider either (I don't mind extra
