On Tue, 2006-01-31 at 12:30 +0000, Richard Huxton wrote:
> Mario Splivalo wrote:
> > When I create a view, I like to define it like this (just representing
> > the form here):
> [snip]
> > But, when I extracit it from postgres, it's somehow stored like this:
> [snip]
> > The later is much more hard to read, and when I need to change the view,
> > i get rash and stuff :)
> >
> > Is there a way to tell postgres NOT to format the 'source code' of my
> > views?
>
> I don't think it stores the "source code", but rather the structure of
> the underlying query. So I'm afraid you lose the spacing.
>
> I keep all my definitions in a set of files and read in updates with \i
> my_filename.sql from psql. That lets me keep all my spaces and comments.
>
Yes, I'm tied to the pgadmin3 for the moment, so there's nothing I could
do. It's a pain to develop a database such way.
Mike
--
Mario Splivalo
Mob-Art
[EMAIL PROTECTED]
"I can do it quick, I can do it cheap, I can do it well. Pick any two."
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
