Thread: Re: where is the "applied"?
Hi Kai, It beats me too. I was under the impression that the patch was applied for all versions greater than 6.3.2. I haven't bothered to upgrade since then so I don't know if it was ever actually applied. Here is a working copy of refint.c which I am using now, you can try using it but I haven't tested it for V6.5. -- Anand. kai qu wrote: > hi, Anand, > > why I can not find it in the source code in V6.5? isn't it applied? Am I > missing something ? > > Kai > > ########################################################## > From: Bruce Momjian <maillist@candle.pha.pa.us> > To: anand@bytekinc.com (Anand Surelia) > Subject: Re: [GENERAL] Foreign Keys: check_primary_function > Date: Sun, 14 Mar 1999 19:34:27 -0500 (EST) > > Applied. > > > Hi All, > > I've changed the check_primary_key() function code to allow for either > > > the "automatic insert key rule" or "dependent insert key rule". > > Previously it restricted the addtion of a child entry if the > > corresponding parent entry was not there. Now if the option is > > "automatic" it will add an entry in the parent too ( it will be > > successful if there are no no-null fields in the parent apart from the > > > primary key). > > The way to use it now is: > > /* > > * check_primary_key () -- check that key in tuple being > > inserted/updated > > * references existing tuple in "primary" table. > > > * Though it's called without args You have to specify referenced > > * table/keys while creating trigger: key field names in triggered > > table, > > * referenced table name, referenced key field names,type of action > > [automatic|dependent]: > > * EXECUTE PROCEDURE > > * check_primary_key ('Fkey1', 'Fkey2', 'Ptable', 'Pkey1', 'Pkey2', > > '[automatic|dependent]'). > > */ > > I am attaching the new ../contrib/spi/refint.c file which will do > this. > > I will be glad to help in case of any problems. > > > > - Anand. > > > >
Attachment
No idea why it isn't in there. Let me know what I should apply. > Hi Kai, > > It beats me too. I was under the impression that the patch was applied for > all versions greater than 6.3.2. I haven't bothered to upgrade since then so > I don't know if it was ever actually applied. Here is a working copy of > refint.c which I am using now, you can try using it but I haven't tested it > for V6.5. > > -- Anand. > > kai qu wrote: > > > hi, Anand, > > > > why I can not find it in the source code in V6.5? isn't it applied? Am I > > missing something ? > > > > Kai > > > > ########################################################## > > From: Bruce Momjian <maillist@candle.pha.pa.us> > > To: anand@bytekinc.com (Anand Surelia) > > Subject: Re: [GENERAL] Foreign Keys: check_primary_function > > Date: Sun, 14 Mar 1999 19:34:27 -0500 (EST) > > > > Applied. > > > > > Hi All, > > > I've changed the check_primary_key() function code to allow for either > > > > > the "automatic insert key rule" or "dependent insert key rule". > > > Previously it restricted the addtion of a child entry if the > > > corresponding parent entry was not there. Now if the option is > > > "automatic" it will add an entry in the parent too ( it will be > > > successful if there are no no-null fields in the parent apart from the > > > > > primary key). > > > The way to use it now is: > > > /* > > > * check_primary_key () -- check that key in tuple being > > > inserted/updated > > > * references existing tuple in "primary" table. > > > > > * Though it's called without args You have to specify referenced > > > * table/keys while creating trigger: key field names in triggered > > > table, > > > * referenced table name, referenced key field names,type of action > > > [automatic|dependent]: > > > * EXECUTE PROCEDURE > > > * check_primary_key ('Fkey1', 'Fkey2', 'Ptable', 'Pkey1', 'Pkey2', > > > '[automatic|dependent]'). > > > */ > > > I am attaching the new ../contrib/spi/refint.c file which will do > > this. > > > I will be glad to help in case of any problems. > > > > > > - Anand. > > > > > > > > [application/x-unknown-content-t is not supported, skipping...] -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Bruce, I would have given you a patch for refint.c (apart from the enhancements it also solves a problem with cascading delete), but I have only 6.3.2 to create a patch against and also because I haven't tested it on v6.5. I am again attaching the refint.c source which I am currently using which can be used to create a patch, if it work with the new version. -- Anand Bruce Momjian wrote: > No idea why it isn't in there. Let me know what I should apply. > > > Hi Kai, > > > > It beats me too. I was under the impression that the patch was applied for > > all versions greater than 6.3.2. I haven't bothered to upgrade since then so > > I don't know if it was ever actually applied. Here is a working copy of > > refint.c which I am using now, you can try using it but I haven't tested it > > for V6.5. > > > > -- Anand. > > > > kai qu wrote: > > > > > hi, Anand, > > > > > > why I can not find it in the source code in V6.5? isn't it applied? Am I > > > missing something ? > > > > > > Kai > > > > > > ########################################################## > > > From: Bruce Momjian <maillist@candle.pha.pa.us> > > > To: anand@bytekinc.com (Anand Surelia) > > > Subject: Re: [GENERAL] Foreign Keys: check_primary_function > > > Date: Sun, 14 Mar 1999 19:34:27 -0500 (EST) > > > > > > Applied. > > > > > > > Hi All, > > > > I've changed the check_primary_key() function code to allow for either > > > > > > > the "automatic insert key rule" or "dependent insert key rule". > > > > Previously it restricted the addtion of a child entry if the > > > > corresponding parent entry was not there. Now if the option is > > > > "automatic" it will add an entry in the parent too ( it will be > > > > successful if there are no no-null fields in the parent apart from the > > > > > > > primary key). > > > > The way to use it now is: > > > > /* > > > > * check_primary_key () -- check that key in tuple being > > > > inserted/updated > > > > * references existing tuple in "primary" table. > > > > > > > * Though it's called without args You have to specify referenced > > > > * table/keys while creating trigger: key field names in triggered > > > > table, > > > > * referenced table name, referenced key field names,type of action > > > > [automatic|dependent]: > > > > * EXECUTE PROCEDURE > > > > * check_primary_key ('Fkey1', 'Fkey2', 'Ptable', 'Pkey1', 'Pkey2', > > > > '[automatic|dependent]'). > > > > */ > > > > I am attaching the new ../contrib/spi/refint.c file which will do > > > this. > > > > I will be glad to help in case of any problems. > > > > > > > > - Anand. > > > > > > > > > > > > > > [application/x-unknown-content-t is not supported, skipping...] > > -- > Bruce Momjian | http://www.op.net/~candle > maillist@candle.pha.pa.us | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026