[HACKERS] Help Required regarding implementing operators in postgreSQL

2007-05-24 Thread Tasneem Memon 

Dear Developers,
Hi, I am Tasneem Memon doing MS Computer Science. I am working on my thesis 
these days, for which I have defined some operators theoritically as well as 
their algorithms, and intend to implement them in PostgreSQL. These 
operators(NEAR, NOT NEAR) are binary and work with NUMBER and DATE data types. 
Now I need to implement support for them in the parser. But I haven't worked on 
the optimization of the operators. And also I am new to database systems 
programming, I am quite confused about what to do now and if I am going the 
right direction!Please Guide me what should I do next.With best regards,
 

Tasneem Ishaque Memon MS (Computer Science) Institute of Mathmetics and 
Computer Science University of Sindh, Jamshoro Pakistan 
http://www.geocities.com/tasneememon/- The process of gaining knowledge is not 
producing results but clearing away ignorance.
_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

Re: [HACKERS] Help Required regarding implementing operators in postgreSQL

2007-05-24 Thread Tom Lane 
Tasneem Memon [EMAIL PROTECTED] writes:
 Hi, I am Tasneem Memon doing MS Computer Science. I am working on my thesis=
  these days, for which I have defined some operators theoritically as well =
 as their algorithms, and intend to implement them in PostgreSQL. These oper=
 ators(NEAR, NOT NEAR) are binary and work with NUMBER and DATE data types. =
 Now I need to implement support for them in the parser. But I haven't worke=
 d on the optimization of the operators. And also I am new to database syste=
 ms programming, I am quite confused about what to do now and if I am going =
 the right direction!Please Guide me what should I do next.With best regards=

It sounds like you could use LIKE and its underlying operators/functions
as a template to follow.

regards, tom lane

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match