Re: DataObject Inserts and Sequences
| From: | Justin Patrin | Date: | Sat, 28 Feb 2004 00:14:27 +0000 |
| Subject: | Re: DataObject Inserts and Sequences | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-11004@lists.php.net to get a copy of this message | ||
Michael Kunze wrote:
Michael Kunze wrote:I've submitted a bug report. It looks to me like this *is* expected behavior, but it seems to me that it really should not be. -- paperCrane <Justin Patrin>rereading every bit of documentation i found this: ignore_sequence_keys = ALL that config option disabled that (to me) odd behavior. thanks for listening.mhh. that was a bit early. turning this feature off for all tables solves it for the tables i had problems before (like player_has_stats (see my previous post)) BUT now it doesn't work anymore for tables that did it right before: player_not_visited_sector: QUERY: INSERT INTO player_not_visited_sector (player_id , sector_id ) VALUES ( 1 , 100 ) although player_id was set to 13! this is a little too much AI for my taste (if you want to call it AI) many primary keys of tables are actually foreign key and sequences are really useless here. if i want a sequence i'll tell it which table should use one, not the other way around. so my solution for now is to turn it off for these tables it does it wrong. only god knows why it does it for some tables only. if someone can enlight me on that? for now i have to assume it's a bug.