be-null problem
was catching me until I added that sequence_names call for the class
metadata. Once that was added, Rose used the sequence appropriately for
generation of the PK values at insert time.
I guess I'm wondering why this step was necessary if the column metadata
itself already indica
ed -- this isn't based on any exhaustive research on my
part and may be an incorrect observation).
If anyone has any experience with this or suggestions to get it working
(beyond "don't use Safe" :) I'd love to hear them.
Thank
king something of an off-the-cuff
observation that I knew might be wrong. I'll reproduce the error I got
and pass it along if it appears somehow inconsistent with what you've
just described.
Thanks.
- Ethan
--
Ethan Rowe
End Point C
t with the meaning
expressed through with_objects.
I was about to dive into this and see if I could could up with a patch
that would do this, but I figured it would be better to correspond with
the list first and make sure I'm not missing something. Am I? :)
Thanks in a
ot enforce referential integrity on its foreign keys, even
> when the columns involved are NOT NULL), then turn off the
> refferential_integrity attribute for the foreign key that links b to
> c:
>
> http://search.cpan.org/dist/Rose-DB-Object/lib/Rose/DB/Object/Metadata/ForeignKey.pm#
d in just table "b" without pulling "c" along with it, meaning I
could arguably get "invalid" b records (if any existed) if I simply
didn't bother with table c in this case. Given t
ss for ways to control this behavior. And
> let me know if it actually works for you guys :)
>
>
Hopefully I'll get to play around with this soon.
Thanks again.
- Ethan
--
Ethan Rowe
End Point Corporation
[EMAIL PROTECTED]
---
