On 7/10/07 1:01 PM, "Bealers" <[EMAIL PROTECTED]> wrote:
> OK, thanks. This got me further along the line and am now able to
> rebuild my database however I am unable to re-import, it falls over
> when pulling the data back in and it seems as if the issue relates to
> matching the foreign keys, for example the record:
>
> Town_63:
> country_id: 4
> town_name: Belfast
>
> gets imported to the town table with an ID of 60! I'm suspecting that
> the import falls over due to some foreign keys not matching up.
>
> The whole propel dumping and re-importing seems very flaky. It's
> really screwed me up too as I've a bunch of schema changes that I've
> been unable to apply.
You don't use the acutal key you use the name designation in the
import_data.yml. Consider the following:
TableOne:
to_record_1:
table_two_id: tt_record_1
other_value: foo bar
TableTwo:
tt_record_1:
value_1: foo
value_2: bar
See how its linked? you use the yml name of the record (ie. to_record_1,
tt_record_1, etc..)
Additionally all you tables need to be in dependency order. Using the
example above TableTwo would have to come before TableOne in your
import_data.yml file so that any records that TableOne might link to will
have been assigned keys before it attempts to link them.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
