The code in the spec is:
person.companies ++= companies
person.save
// Break some joins
companies(3).delete_! // delete 4
companies(6).delete_! // delete 7
person.companies.refresh // reload joins so joinEntity.company.obj
isn't cached
person
My plan is to make FKs
Ah, I see.
Where does MappedManyToMany delete anything not in the join table? If you mean
the spec feel free to change it or comment out the whole thing and ask me to
fix it. By the way it's hardcoded to use H2MemoryProvider.
Is OneToMany doing anything bad?
Thanks.
Are FKs not created using a Driver that supports it? schemify calls
ensureConstraints which seems to do it, no?
-
Derek Chen-Beckerdchenbec...@gmail.com wrote:
If FKs are enabled then the spec fails because you're intentionally trying
to break the joins by
Currently ensureConstraints calls DriverType.supportsForeignKeys_?,
defaulting to false. The ticket that I'm working on is because none of the
drivers seem to override that. The current MappedManyToMany throws an FK
violation exception because it tries to delete one side of the Many-To-Many
If FKs are enabled then the spec fails because you're intentionally trying
to break the joins by deleting the Companys that are on the other side of
the many-to-many. I'm not sure that FKs should be enabled by default, but if
I add the option to introduce them with schemify then I could write
OK, I've run into a snag. Schemifier does support foreign key creation, as
do most of the database vendors. The ManyToMany Mapper support, however,
seems to expect no foreign key constraints, since it's explicitly testing
broken refs in the ManyToManySpecs tests:
ManyToMany should {
skip
OK, I've run into a snag. Schemifier does support foreign key creation,
as do most of the database vendors. The ManyToMany Mapper support,
however, seems to expect no foreign key constraints, since it's
explicitly testing broken refs in the ManyToManySpecs tests:
I do not really know
Absolutely. I have a PG 8.0, 8.1 and 8.3 instance set up for testing on my
home box because of the last time I made a PG-related change.
Derek
On Thu, Dec 3, 2009 at 2:48 PM, David Pollak
feeder.of.the.be...@gmail.comwrote:
On Thu, Dec 3, 2009 at 1:47 PM, Derek Chen-Becker
I agree on both points (foreign keys and documentation). Please open a
ticket asking for proper foreign key support and I'll work on it next
week.
http://github.com/dpp/liftweb/issues/#issue/224
Julian
--
You received this message because you are subscribed to the Google Groups
Lift
I agree on both points (foreign keys and documentation). Please open a
ticket asking for proper foreign key support and I'll work on it next week.
Derek
On Wed, Dec 2, 2009 at 6:05 PM, Julian Backes
julianbac...@googlemail.comwrote:
Hi Derek,
It's been a long time since I looked at that
On Thu, Dec 3, 2009 at 1:47 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
I agree on both points (foreign keys and documentation). Please open a
ticket asking for proper foreign key support and I'll work on it next week.
Please make sure it works on PG 8.0/8.1 as there is at least 1 Lift
It's been a long time since I looked at that particular code, so I may have
misspoke. Having said that, if it's currently disabled in the driver I'm not
sure why and I would want to review it before saying that it works properly
in all cases.
Derek
On Sun, Nov 29, 2009 at 1:11 PM, Julian Backes
Hi Derek,
It's been a long time since I looked at that particular code, so I may
have misspoke. Having said that, if it's currently disabled in the
driver I'm not sure why and I would want to review it before saying that
it works properly in all cases.
I think the problem here is that the
Hi Lift Community,
this is a reply to my own question:
I'm trying to get my first scala/lift app working and I have a
problem: Schemifier.schemify(...) creates everything, i.e. tables,
primary keys, indices but it does not create the foreign key
constraints.
After hours of compiling and
Hi,
I'm trying to get my first scala/lift app working and I have a problem:
Schemifier.schemify(...) creates everything, i.e. tables, primary keys,
indices but it does not create the foreign key constraints.
I've seen in Schemifier.scala SQL code for generating foreign key
constraints so I
15 matches
Mail list logo
