Anyways, I was definitely screwed up ... forcing maven to actually do
what it was supposed to fixed my problem. Thanks for the pointer
Marius.
~Thomas
On Sat, Oct 3, 2009 at 5:39 PM, Thomas Rampelberg wrote:
> I thought that I'd just updated all the versions . from that stack
>
> Br's,
> Marius
>
> On Oct 3, 11:11 pm, Thomas Rampelberg wrote:
>> I just synced up to main this morning and now whenever I try and use
>> one of my snippets, I'm getting the traceback below. Any hints on what
>> I'm doing wrong? The snippet in questi
I just synced up to main this morning and now whenever I try and use
one of my snippets, I'm getting the traceback below. Any hints on what
I'm doing wrong? The snippet in question is just the basic
Util.in/Util.out that the tutorial has you write.
I had some issues getting string foreign keys working that required
changes to MetaMapper (because of how it handles autogenerated primary
keys). That said, Here's some code that'll fix the issue you're
currently having:
class StringForeignKey[T<:Mapper[T],O<:KeyedMapper[String, O]](
override v
Are you extending your table class with OneToMany[Long, ClassName] ?
Both of those are included in the OneToMany trait itself. ex:
class Foo extends LongKeyedMapper[Foo] with OneToMany[Long, Foo]
Sorry about forgetting to include that in my previous post =/
On Fri, Sep 25, 2009 at 11:11 AM, ben
This is really great, making XML as easy to generate as JSON was
something I thought I'd never see.
On Fri, Sep 25, 2009 at 7:27 AM, David Pollak
wrote:
>
>
> On Fri, Sep 25, 2009 at 6:19 AM, Timothy Perrett
> wrote:
>>
>> Sorry Dave, but the brevity of your reply left me somewhat confused...
>
Ahhha, I guess I've not been trying to actually delete any fields. Thanks!
On Thu, Sep 24, 2009 at 4:48 PM, David Pollak
wrote:
>
>
> On Thu, Sep 24, 2009 at 4:46 PM, Thomas Rampelberg
> wrote:
>>
>> David, just to make sure that I know what I'm talking abo
David, just to make sure that I know what I'm talking about, if you
set writePermission_? to false for each field, you could emulate the
behavior?
On Thu, Sep 24, 2009 at 4:41 PM, David Pollak
wrote:
> There's no read-only support for tables in mapper at this time. Sorry.
>
> On Thu, Sep 24, 2
You can ..
override def writePermission_? = false
(On a per-field basis)
On Thu, Sep 24, 2009 at 2:52 PM, andythedestroyer
wrote:
>
> This may be obvious but I am having trouble setting this up.
>
> I need to map a database view which isn't a problem because I just set
> it up as I would a
You can do this with Mapper using a ManyToMany relationship. To make
sure we're talking about the same thing, let me try and explain.
With ManyToMany, you can do both Person.find(By(Person.name,
name)).map(_.skills) as well as Skills.find(By(Skill.description,
description)).map(_.people) and get
I'd suggest a one to many relationship with a foreign key. For
something off the top of my head (no guarantees this'll actually
work):
class Person extends LongKeyedMapper[Person] with IdPK {
def getSingleton = Person
object skills extends MappedOneToMany(Skills, Skills.person) with
Owned[Sk
sion, please
> see:
> http://groups.google.com/group/liftweb/browse_frm/thread/0c7a97cbf60780f0?hl=en#
>
> The current state of mapper's primary key support is sub-optimal. There
> have been a couple of discussions of the issues on-list. I am hoping to
> spend some time on thi
I've been working at getting MetaMapper to work with primary keys that
aren't auto-generated (or longs). Towards this end, I've got a patch
for MetaMapper.scala that I'd like to get in. Who could I talk about
the process for that?
In addition, as part of implementing the functionality, I ran into
13 matches
Mail list logo
