> Do we really need a cache?
Need... It seems smarter than invoking the same query over and over
again. In our case 240 times.
> Is it a network roundtrip problem or the query on the database?
> What might work to reduce the query
> metaData.getTables(factory.getCatalog(), databaseName, tableName, new
> String[] { "TABLE", "VIEW" } )
This seems also a nice enhancement.
> A problem I have seen with db drivers is that the name lookup takes very
> long for the db host. The oracle driver for example will always try to
> find an ip-address even when you use an ip-address as hostname. WHen it
> is a lookup problem then you will see a thread stack (In a thread dump,
> kill -3) waiting on a lookup call of a socket
While using the cache this won't be a bug issue anymore.
> Another problem I see with the current code is that multiple schemas in
> the same database can have the same table name. A getTables could return
> a table from a different schema.
*wow*, in our case we didn't trigger this bug because we are always
using basenames... But it seems smart to specify the databaseName,
maybe Marcel will add this bug to his proposal.
Rob
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
