efleming969 wrote:
> I saw that syntax on a blog a few days ago, but I did not try it with
> version 7.6.
>
> The db4o team has been really dedicated to C# and LINQ in the past few
> versions, to I would image the library will become more friendly to
> languageas like Scala.
>
Unfortunately, DB4O's choice of license and business model drives them
away from JVM-land and toward CLR-land.
I've had pretty extensive chats with the DB4O people and would really
like to do something with them related to Lift, but it's a huge challenge.
DB4O is dual-licensed under a GPL variant and commercial. In order to
do any commercial development at all (according to the DB4O sales
people), one must buy a commercial license. But buying a commercial
license is hard. I spent more than a week in round-and-round
discussions with DB4O sales just to get a price list. Basically, it was
going to cost about $10K for my development licenses. This was a
development license just to explore and see if DB4O was right for the
project that I was working on. Yes, I know... I could have just
downloaded the code and tested it out, but I believe in abiding by
license terms.
What this means is that people can't just play with DB4O in a commercial
setting... they have to plunk down cash. This is normal in
Microsoft/CLR land, but most JVM-based projects, even in corporate
settings, are prototyped with open source code. When things get closer
to production, the companies buy support and indemnification from the
open source vendors.
So, I'd like to do something with DB4O. They'd like to do something
with Lift. But nobody's found the right ground or the right business
model to make things work. Sigh.
David
> On Oct 6, 12:08 am, "Bjarte S. Karlsen"
> <[EMAIL PROTECTED]> wrote:
>
>> efleming969:
>>
>>
>>
>>
>>> I've added a project to github under the name of liftyourdb4o.
>>>
>> I looked at db4o in the #scala channel and got this nice query method to
>> work. It needs db4o 7.6 though (I tried with 7.4 and it fails since the
>> match method retuns an Object and not a T), since it has a fix that allows
>> match to get an Object.
>>
>> def query[T](filter:T => boolean) = {
>> db.query(new Predicate[T]() {
>> def `match`(entry: T): boolean = {
>> filter(entry)
>> }
>> });
>> }
>>
>> So basically you could do
>>
>> val result = query[Course](_.name.equals("Scala"))
>>
>> --
>> With kind regards / Med vennlig hilsen,
>> Bjarte Stien Karlsen (GPG: 0x626B2F3A)
>> To find out the limits of the possible you have to go beyond them into the
>> impossible.
>>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
