Re: [HACKERS] More PostgreSQL+CORBA
От | Hannu Krosing |
---|---|
Тема | Re: [HACKERS] More PostgreSQL+CORBA |
Дата | |
Msg-id | 364EDFDF.A08EE918@trust.ee обсуждение исходный текст |
Список | pgsql-interfaces |
Ok, moved to interfaces as suggested Maybe it would be a good idea to strip CC:s ? Michael Robinson wrote: > > > > As for 6-9 months...I think this is more in Michael court then > >anything...I don't see why work can't start on it now, even if its nothing > >more then Michael submitting patches that have the relevant sections > >#ifdef's so that they are only enabled for those working on it. I don't > >imagine this is going to be a "now it isn't, now it is" sort of thing...it > >might take 6-9 months to implement... > > This is my plan: > 1. Wrap the current libpq API in CORBA, as a proof of concept Add 1.A. here: extend current FE<->BE interface to support prepared statements, at least to the level of SPI, maybe even _start_ from "extended" SPI CORBA interface. "Extended" because SPI had same deficiences as well compared to the "main" FE<->BE protocol. > 2. Implement a static row-level interface, which maps PostgreSQL > types to CORBA types 2.A. Define a standard way for CORBA'fying the postgresql user-defined types > 3. Design a fully dynamic interface, complete with Interface > Repository integration with the PostgreSQL type system > 4. Implement the design > > Number one shouldn't take very long (a few weeks, once I get the whole > CORBA development thing sorted out). Two shouldn't take much longer. > Three and four is anybody's guess, and, as I mentioned earlier, four > depends on currently unimplemented sections of ORBit. I think, that we should start with an ORB that has C-interface 'cause the rest of PostgreSQL is in C. The time will probably be better spent on implementing the unimplemented sections rather than writing a C to C++ wrapper (the part which should in theory be made unneccesary by CORBA !) So supporting other language IDL mappings (C++,java,python,ada,smalltalk,...) directly in backend seems not to be a very good idea Of course we should support all C mappings. ------------------ Hannu
В списке pgsql-interfaces по дате отправления: