Thread: ecpg changes
Okay, I've updated the ecpg parser yet again. Unfortunately it has one remaining shift/reduce conflict. But the very same conflict is in gram.y, so I don't dig into it very much now. Anyway, I just saw that there were minor changes made to ecpg by others. Now I like that but I would prefer if I was told about that. Otherwise my version numbering and Changelog maintaining might break. Or simply change these too. :-) Also I had to add #include <errno.h> to backend/libpq/pqcomprim.c to be able to compile postgresql. Patch is attached. Since my resubscription process is still not finished yet, I still send them here. Michael -- Michael Meskes | Go SF 49ers! Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire! Tel.: (+49) 2431/72651 | Use Debian GNU/Linux! Email: Michael.Meskes@gmx.net | Use PostgreSQL!
Applied. > Okay, I've updated the ecpg parser yet again. Unfortunately it has one > remaining shift/reduce conflict. But the very same conflict is in gram.y, so > I don't dig into it very much now. > > Anyway, I just saw that there were minor changes made to ecpg by others. Now > I like that but I would prefer if I was told about that. Otherwise my > version numbering and Changelog maintaining might break. Or simply change > these too. :-) > > Also I had to add #include <errno.h> to backend/libpq/pqcomprim.c to be > able to compile postgresql. I had taken care of that last night. > > Patch is attached. Since my resubscription process is still not finished > yet, I still send them here. -- 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, Pennsylvania19026