Re: Call for an API standard for SQL statements

"Fredrik Bertilsson" <fredrik_bertilsson_at_passagen.se> wrote in message news:31f7e57d.0410202106.3112dcd6_at_posting.google.com...
> "Marshall Spight" <mspight_at_dnai.com> wrote:
>
> > The problem with this idea is that the object model would
> > be more cumbersome than the SQL strings, even in a language
> > that isn't great at string handling. I've tried this several times;
> > I now believe it is not a good idea.
>
> I am using an (non-standardized) object model now for making queries
> and I don't agree that it is more cumbersome than writing SQL
> statements as string. It is about the same amount of lines of code and
> if you are using a flexible script language like python the code can
> be rather nice and clean. I think it is more about what you are used
> to do.

I am used to manipulating objects, which is why it was such a surprise to me that after several attempts I wasn't able to make an object framework that was as easy to use as just typing in SQL.

Perhaps it is you that has an issue with not being used to SQL.

> But the main purpose for having an object model is not to make the
> query building more compact. The purpose is the let the database
> framework have knowledge about how the query is constructed, which
> makes a lot of extra features in the framework possible.

Such as?

Marshall Received on Thu Oct 21 2004 - 10:51:02 CEST