Re: postgresql module (was : Re: [Perfparse-devel] Using indexes with mysql)

[Ben C. <Be...@cl...>]

So, question:-

To make code slightly more uniform.  What do we use for a date/time:

DATETIME	Suffers problems Flo demonstrated.
		But each module has own code, may not be significant.
INT		Limited to 1970 -> ~2035
DOUBLE		Unlimited, can also use decimal part for milli-seconds.
		But hard to use with time.h.

Yves was going to propose a method for making the 'c' CGI SQL easier to 
port.  I would be interested.

Regards,

Ben

Yves Mettier wrote:

>>Hi again,
>>
>>to show that handling date datatypes in different RDBMS is not easy
>>portable, here some syntax examples (copied from sqlzoo.net):
> 
> 
> [...]
> 
> 
>>So you see, it's really hard to use ANSI SQL :-) But perfparse does not
>>use to many of the special cases, so i think it will be easier to make it
>>db independent.
> 
> 
> [...]
> 
> Remember that with modules, you can do something very different from one db module to
> another. You don't need to follow the same database schema if you don't want to.
> 
> Too much different modules is bad (more work, more bugs...)
> But if you need speed and space, don't try to be 100% compatible. The mysql module will
> never connect to a postgresql database :)
> 
> And again, the main problem that you will have is in the CGIs : they don't use modules.
> I have ideas for the CGIs and we can talk about that when you want.
> 
> Yves