Login | Register
My pages Projects Community openCollabNet

propel
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author matthewh
Full name Matthew Hershberger
Date 2004-04-12 13:16:02 PDT
Message Hello everyone,

I've noticed a trend in the propel where problems that will occur in
insert-sql are not shown as errors/warnings during the phing build
phase. Is this just missing error handling or is there some other
reason?

Thanks,

Matt

On Apr 12, 2004, at 15:42, Hans Lellelid wrote:

> Hi Matt & Denny,
>
> I applied the fix below to the foreignkey.tpl template. If you update
> from CVS this should be there.
>
> I ended up using Matt's code w/o modification:
>
>> <?php foreach ($table->getForeignKeys() as $fk) { ?>
>> INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
>> FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
>> <?php echo $fk->getForeignTableName() ?> (<?php echo
>> $fk->getForeignColumnNames() ?>),
>> <?php } ?>
>
> since MySQL/InnoDB does not complain if you define an index more than
> once. That made it easier than needing to check to see whether index
> already existed -- and I wasn't completely sure what would happen if
> column was part of another multi-column index, etc. We'll keep it like
> this unless someone has trouble with it.
>
> Thanks,
> Hans
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org