On Wednesday, March, 2001-03-28 at 16:55:55, will trillich wrote:
> On Thu, Mar 29, 2001 at 12:17:31AM +0200, Marek Pętlicki wrote:
> > On Tuesday, March, 2001-03-27 at 21:42:39, markus jais wrote:
> > >
> > > in MySQL I can type something like in Bash on my linux box:
> > >
> > > $ mysql -u root -p < file.sql
> > >
> > > then the file file.sql is read.
> > >
> > > can you tell me how to do this with postgresql???
> > > thanks a lot.
> >
> > very similar:
> >
> > psql dbname username < file.sql
> >
> > should work
> >
> > (you can well omit username if it is the same as your login name)
>
> if your sql is flawless, go right ahead.
>
> since psql reads "<file" from its STDIN, it won't include any
> line numbers to help you track down troubles. (as far as it's
> concerned, you're just typing reeeeal fast, so the feedback would
> occur right as you type, so line numbers would be superfluous.)
>
> on the other hand, both
>
> psql -f file-containing-sql mydb
>
> and
>
> psql mydb
> mydb=> \i file-containing-sql
>
> will spit out error messages including line numbers to help you
> debug your sql.
off course, but note that the question was if one could use '< file.sql'
It is the same mechanism as issuing:
my_program_creating_sql | psql dbname username
(for example to use compressed dump to restore without decompressing it
to the disk first) which can't be done with -f option ;-)
Nevertheless your remark about debugging errors in sql files is very
important...
regards
--
Marek Pętlicki <[EMAIL PROTECTED]>
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
