The New Database Compatibility Layer

[Vlad Dascalu]

Are you sure about that?

I mean, would a MySQL developer that added a Mysql.pm function notice 
that such function doesn't exist in the PySQL module? As far as I 
understand, the code should be modular in the sense that it loads only 
the right module suitable for the right database type, so for example 
only the Mysql one will be looked upon. The lack of function in the 
other modules will go unnoticed until someone using PySQL will see an error.

Vlad.

Max Kanat-Alexander wrote:

>On Wed, 2005-02-16 at 15:06 -0500, David Miller wrote:
>  
>
>>Do we have a test in the test suite which ensures that all of the DB 
>>modules we ship are currently in compliance with the list of required 
>>overrides?  (So tinderbox will go red if someone checks in a patch that 
>>doesn't update all of them)
>>    
>>
>
>	Well, the code *itself* actually checks that all the functions exist,
>every time that you instantiate that type of DB. So even developers who
>aren't using runtests will see an immediate failure.
>
>	However, having that as part of the testsuite would also be a good
>idea.
>
>	-Max
>  
>