"Robert B. Easter" wrote:
>
> > you can't do that with a cursor, but you can use they mysql-ism called a
> > limit clause. for example, to fetch rows 26-50 from that query, you'd
> > do:
> >
> > select * from films limit 25,26;
> >
> > or
> >
> > select * from files limit 25 offset 26;
I did kn
Hello,
I have a strange problem with 'like' behaviour
when I upgrade from 6.5 to 7.0
Here is my table :
create table persistent_config (
key varchar primary key,
typevarchar(12),
value varchar not null
)
and its content :
base=# select * from pe
KuroiNeko wrote:
> > I wonder if there couldn't borrowed some code from Interbase which has
> > full featured stored procedures - at least it was told to me that it has
> > ...
>
> Well, I have some hands-on experience with IB, don't know whether this is
> perfectly relevant, but here goes
Josh Berkus wrote:
> Tom, Bruce, Jan, etc.:
>
> [...]
>
> The rest of these requests apply to 7.2:
>
> 2. Stored Procedure functionality, i.e. outputting a full recordset from
> a function (or new structure, if functions are hard to adapt) based on
> the last SELECT statement passed to the functio
Jan,
> To put the ball back into your yard, I'd like to
> make a
> request too. There seem to be alot people using
> PL/pgSQL
> and/or PL/Tcl extensively. OTOH there are newbies
> again and
> again asking for a good tutorial, programming
> examples and so
> on. Wri
> PL/pgSQL parses the entire function body at first call (per
> backend). But the SPI querystrings for all the statements
> aren't parsed at that time. It uses SPI_prepare() only for
> expressions and queries that actually get executed, so that a
> huge function that is called
* Jan Wieck <[EMAIL PROTECTED]> [001117 08:26]:
> > triggered the error would be enormously helpful (I can't tell you the
> > number of times I've gotten "Error at or near ')'" in a huge DDL
> > statement.
>
> That's a general problem of a lex/yacc parser and I'm not
> sure how to for
On Wed, 15 Nov 2000, Jan Wieck wrote:
>
> To put the ball back into your yard, I'd like to make a
> request too. There seem to be alot people using PL/pgSQL
> and/or PL/Tcl extensively. OTOH there are newbies again and
> again asking for a good tutorial, programming e
On Fri, Nov 17, 2000 at 10:06:17AM -0600, Roberto Mello wrote:
>
> I have this on the way. I started creating such document a
> couple months ago when I was porting stuff from Oracle to PostgreSQL and
> stumbled on the few examples on the documentation. I'd be glad to finish
> it up, add mo
I'm trying to find the nearest locations to a certain point using 2 tables.
One contains the address and zipcodes of the locations and is about 2000
rows, the other contains zipcodes and lat, lon values and has about 1.4M
rows.
I've got indexes on the zip column of both tables and I just need to
Roberto -
> > I have this on the way. I started creating such document a
> > couple months ago when I was porting stuff from Oracle to PostgreSQL and
> > stumbled on the few examples on the documentation. I'd be glad to finish
> > it up, add more things to it and then put it somewhere for r
Hmm. Have you VACUUM ANALYZED the tables? If so, what do you get from
these queries:
select attname,attdisbursion,s.*
from pg_statistic s, pg_attribute a, pg_class c
where starelid = c.oid and attrelid = c.oid and staattnum = attnum
and relname = 'zips';
select attname,attdisbursion,s.*
from p
> Hmm. Have you VACUUM ANALYZED the tables? If so, what do
> you get from
> these queries:
Tom, thanks for the reply, and here is all the info you asked for.
> select attname,attdisbursion,s.*
> from pg_statistic s, pg_attribute a, pg_class c
> where starelid = c.oid and attrelid = c.oid and
"Ingram, Bryan" <[EMAIL PROTECTED]> writes:
>> Also it would be useful to see the full declarations of the tables
>> and their indexes; I'm wondering what datatype the zip columns are,
>> for example.
> Table= atms
> | zip | text |
> T
I said:
> Ah, there's your problem --- the planner is not very smart about
> optimizing cross-datatype comparisons. Make these columns both text,
> or both varchar, and I'll bet you get a more intelligent plan.
After a little further thought, I realize that the planner may be
handicapped by not
On Friday 17 November 2000 04:01, Arnaud Vandyck wrote:
> "Robert B. Easter" wrote:
> > > you can't do that with a cursor, but you can use they mysql-ism called
> > > a limit clause. for example, to fetch rows 26-50 from that query,
> > > you'd do:
> > >
> > > select * from films limit 25,26;
> >
"Robert B. Easter" wrote:
> If someone has done it a better way, I'd like to hear how. However,
> sometimes it is possible to cache a count(*) value somewhere in the database
> so it doesn't have to be found everytime - it depends on your database and
> what the select is if you can store the co
17 matches
Mail list logo
