In article <[EMAIL PROTECTED]>,
Jochem van Dieten <[EMAIL PROTECTED]> writes:
> Since the is no requirement to have an accessible DEFINITION_SCHEMA
> there may be a mechanism to recreate the definition on the fly from
> other information, but the same goes for the other view related base
> tables
On 05 Oct 2004 12:02:44 +0200, Harald Fuchs wrote:
> "Martijn Tonies" <[EMAIL PROTECTED]> writes:
>>
>> 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?
>
> I disagree. A proper information_schema implementation is much
On 05 Oct 2004 11:46:18 +0200, Harald Fuchs wrote:
> "Martijn Tonies" writes:
>>
>> 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 My
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 -
In article <[EMAIL PROTECTED]>,
"Martijn Tonies" <[EMAIL PROTECTED]> writes:
> 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.
>>
>>
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 inclu
In article <[EMAIL PROTECTED]>,
"Martijn Tonies" <[EMAIL PROTECTED]> writes:
> 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, sto
> > I suppose these are the ways with Databases. They don't work the way
> > we like them to.
> > So please adjust with it. For this matter I think, any RDBMS will be
> > doing their or paddings to the scripts when they are loading it in
> > memories.
>
> But that doesn't make it right.
>
> Specif
On Tue, 5 Oct 2004 00:27:45 +0530, Eldo Skaria wrote:
>
> I suppose these are the ways with Databases. They don't work the way
> we like them to.
> So please adjust with it. For this matter I think, any RDBMS will be
> doing their or paddings to the scripts when they are loading it in
> memories.
Hello Eldo,
> I suppose these are the ways with Databases. They don't work the way
> we like them to.
> So please adjust with it. For this matter I think, any RDBMS will be
> doing their or paddings to the scripts when they are loading it in
> memories.
> just the same way for oracle(where i have
Hai Martin,
I suppose these are the ways with Databases. They don't work the way
we like them to.
So please adjust with it. For this matter I think, any RDBMS will be
doing their or paddings to the scripts when they are loading it in
memories.
just the same way for oracle(where i have some (in)exp
Hi there,
I'm testing MySQL 5.0.1 a bit - and I noticed the following...
When executing this:
create view myview2 (t0)
as select c1 from t
It returns this when doing a SHOW CREATE VIEW myview2:
CREATE VIEW test.myview2 AS select `test`.`t`.`c1` AS `t0` from `test`.`t`
This is not at all what I
12 matches
Mail list logo
