Re: couple bugs with schema

On 1/13/06, Jacob Smullyan <[email protected]> wrote:
> On Thu, Jan 12, 2006 at 05:47:35PM -0700, Jonathan Ellis wrote:
> > autoschema(schema='xxy') returns classes found in schema xxy, but if
> > there is a table with the same name defined in the public schema for
> > any of those classes, name, it will return the definition from the
> > table in public.
>
> Actually, that isn't exactly what is happening, although that can be a
> symptom.  The problem is the "guesscache", which stores the table
> structure for classes in disk files keyed by package/classname and
> which is used by default.  Unless you pass in a different module to
> use, the classes think they live in pydo.base (they don't, but they
> don't know any better) and the guess cache entry for
> pydo.base.Whatever_table will be used regardless of schema (because
> the schema isn't part of the class name).  So, whichever schema is
> autoschema-ed first would generate the first cache entry and
> subsequent calls for the same class name in the same module would use
> it.

Ah, that makes sense.  Okay.

> Second, how to fix.  The way in which the guesscache generates paths
> for objects it stores should be modified so that it is schema-aware.
> I'll do this.  I also wonder whether the guesscache should be used by
> default anyway, for autoschema and for column-guessing.

Thanks.

BTW, when are you planning to take this out of beta?  Seems like it's
been pretty stable since November.

-Jonathan


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click