Hello Harald, others,
> > This is plain rubbish. See my other example with a more complicated
> > view source. When adjusting the view, or extracting a script - the
> > view source becomes complete gibberish.
>
> > MS SQL, or Firebird, for example, store the view-source as defined -
> > this includes comments, spacing etc etc... In short: it becomes usuable.
>
> > MySQL should do this too. From reading these lists, I think MySQL
> > only stores the resulting structure - or something similar - and
> > (currently) not the view source. To make views useful, better change
> > it... :-)
>
> Nope. A standards-compliant database is _required_ to store the
> structure of its objects in its internal information_schema, not some
> SQL string. Of course MySQL isn't standards-compliant at all, but we
> should not make it worse by imitating the quirks of other DBMSs.
I'm unsure what to make of this statement --
I was asking if the view-source can be stored, so that it can be retrieved
the way I created it. Do you agree or disagree?
(and well, MySQL doesn't have an information schema yet, so that's
a no-go area right now).
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
