PDA

View Full Version : Re: feedback on standalone search/playlist toolidea?advanced_search.xml ?



=?ISO-8859-1?Q?Fr=E9d=E9ric_Thomas?=
2005-02-11, 13:03
> That's what I see as the beauty of the DB foundation. Where
> SlimServer used to *be* the database, now it's just a client that
> controls my Squeezebox. I can hit the DB directly for custom queries
> and assemble any arbitrary output format I need. Makes for much
> lighter-weight ancilliary apps like the one you're envisioning.

Well, doing so means the DB becomes another official API of the
SlimServer software, which may not be what SlimDevices want, given it
entails constraints on changes, documentation, etc.

I am sure Dean will give us the offical word on this...

Fred

dean
2005-02-11, 23:52
On Feb 11, 2005, at 12:03 PM, Frédéric Thomas wrote:

> > That's what I see as the beauty of the DB foundation. Where
> > SlimServer used to *be* the database, now it's just a client that
> > controls my Squeezebox. I can hit the DB directly for custom
> queries
> > and assemble any arbitrary output format I need. Makes for much
> > lighter-weight ancilliary apps like the one you're envisioning.
>
> Well, doing so means the DB becomes another official API of the
> SlimServer software, which may not be what SlimDevices want, given it
> entails constraints on changes, documentation, etc.
>
> I am sure Dean will give us the offical word on this...
Ha! You guys are way ahead of me on this.

I'm not sure we're ready to say that direct access to the database is
an official API. I certainly don't expect the DB schema to be fixed
in the near future.

I'd like to hear some discussion on this point...

vidurapparao
2005-02-14, 12:37
dean blackketter wrote:

>
> On Feb 11, 2005, at 12:03 PM, Frédéric Thomas wrote:
>
>> > That's what I see as the beauty of the DB foundation. Where
>> > SlimServer used to *be* the database, now it's just a client that
>> > controls my Squeezebox. I can hit the DB directly for custom queries
>> > and assemble any arbitrary output format I need. Makes for much
>> > lighter-weight ancilliary apps like the one you're envisioning.
>>
>> Well, doing so means the DB becomes another official API of the
>> SlimServer software, which may not be what SlimDevices want, given it
>> entails constraints on changes, documentation, etc.
>>
>> I am sure Dean will give us the offical word on this...
>
> Ha! You guys are way ahead of me on this.
>
> I'm not sure we're ready to say that direct access to the database is
> an official API. I certainly don't expect the DB schema to be fixed
> in the near future.
>
> I'd like to hear some discussion on this point...

I think it's quite likely we will continue to evolve the DB schema - the
upgrade mechanism allows us to do this cleanly. My guess (and it's just
a guess at this point) is that we probably won't substantially change
the entity-relationship model for the 6.x family of SlimServer, but we
will definitely add and remove columns from tables.

It's also possible that we may make use of features such as Class::DBI
triggers
(http://search.cpan.org/~tmtm/Class-DBI-0.96/lib/Class/DBI.pm#TRIGGERS),
essentially requiring all database writes to go through a common API to
maintain database integrity.

I don't think it's unreasonable for an external application that is
flexible enough to deal with an evolving schema to execute queries
directly on the database, but I would strongly recommend against writing
directly.

--Vidur