W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2007

[whatwg] SQL API + access to tables

From: Brady Eidson <beidson@apple.com>
Date: Fri, 19 Oct 2007 21:13:54 -0700
Message-ID: <910EEB05-AC65-4DC8-93B2-74F385963771@apple.com>

On Oct 19, 2007, at 8:08 PM, Scott Hess wrote:

> On 10/19/07, Brady Eidson <beidson at apple.com> wrote:
>> There is no standard way in SQL that I know of to get the list of
>> tables in a database.
>>
>> In SQLite you can enumerate tables out of sqlite_master, but that
>> should not be encouraged.
>>
>> What are people's thoughts about adding this to the API?
>
> This seems way beyond where this spec should go.  If SQLite doesn't
> have a way to enumerate tables which can be encouraged, a way should
> be added to SQLite (I've considered building some introspection
> virtual tables for this kind of thing).

Like I said, you can enumerate tables out of SQLite.  I claim "it  
should not be encouraged" because it involves very SQLite specific  
mechanisms that are not at all portable to any SQL implementation   
other than SQLite.  In fact, we plan to disallow access to the  
sqlite_master table because there's no reason the client *should* be  
able to access such an implementation specific field that has nothing  
to do with "client side database storage"

Nowhere in the spec have we said "the user agent must use SQLite" but  
if we intend web developers to use SQLite specific features to get at  
a "list of tables", then we're encouraging incompatibilities with non- 
SQLite back ends.  Which is something a new spec should not do!

~Brady
\
Received on Friday, 19 October 2007 21:13:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:37 UTC