novice wrote:
2008/11/20 Rodrigo E. De León Plicet <[EMAIL PROTECTED]>:
On Wed, Nov 19, 2008 at 10:03 PM, novice <[EMAIL PROTECTED]> wrote:
sorry I get nothing :(
Of course not. None of the dates you gave in the example overlap.
But it should still have the 1st entry with the name Ben? Am
At 03:34 PM 11/11/04, Geoffrey wrote:
Bruno Wolff III wrote:
On Thu, Nov 11, 2004 at 10:04:30 -0500, Terry Lee Tucker
<[EMAIL PROTECTED]> wrote:
Greetings,
Here is a simple question:
Is it ok to put a unique index on the oid for my tables? We are in
the process
Yes, but you may occasionally have in
I have a machine with OpenBSD 2.6 and PSQL 6.5.3 that allows the use of
up-arrow to retreive/edit previous commands.
I recently built a new machine with OpenBSD 2.8 and PSQL 7.0.2 (from
package) and this feature is GONE!
Is there some way to get this functionality back (hopefully without
changin
At 11:10 AM 5/9/01 +0200, DaVinci wrote:
>On Wed, May 09, 2001 at 10:31:27AM +0200, Renaud Thonnart wrote:
>> How can I delete them in keeping integrity in the database?
>
> drop index?...
Dropping the index will not maintain the PK integrity...
http://www.ca.postgresql.org/users-lounge/docs/7.1
select * from table where last_name ~ '^[A-F]';
or
select * from table where last_name between 'A' and 'G';
or
select * from table where last_name >='A' and last_name<'G'
The second one is broken if last_name='G' returns something.
Use ~* in first example to ignore case.
>>Frank asked: What's this 'CONFIRM' message all about anyway?
>
>Scappy replied: It was just me attempting to fix ppls
>subscription settings after the upgrade, without realizing
>it would email out to everyone ... sorry about that :(
>>Frank: Does this mean we don't actually do the CONFIRM's
Thanks! vacuum did get rid of those messages. The last time
import/rebuild worked it took over 2hrs, now it's down to 30min!
But the original problem ...
I'm finally starting to get some log entries, but they are in
/var/pgsql/log instead of /var/pgsql/postmaster.log - any ideas? probably
an
Thanks! 2>&1 was already used in same script. pgwrap is an OpenBSD thing
that sets pg environment for root user (I know a *little* bit about my
system).
Frank
At 12:49 PM 10/17/00 -0400, you wrote:
>Frank Bax <[EMAIL PROTECTED]> writes:
>> Thanks. When I remove -S
Thanks. When I remove -S then the command never completes?
How do I redirect stderr?
At 11:49 AM 10/17/00 -0400, you wrote:
>Frank Bax <[EMAIL PROTECTED]> writes:
>> I've got the following line in /etc/rc.local on my OpenBSD 2.6 system:
>> /usr/local/bin/pgwrap -o /v
At 06:13 AM 4/14/00 -0500, you wrote:
>I'd think some how there could be a way to vacuum without having to lock
>up the entire DB.
>From http://www.postgresql.org/docs/user/sql-vacuum.htm
>
>VACUUM serves two purposes in Postgres as both a means to reclaim
>storage and also a means to collect in
At 05:35 PM 4/06/00 -0700, you wrote:
>select from a table several records and group by a date column.
just cast your datetime or timestamp (hour) field into a date...
select hour::date, sum(whatever) from table group by hour::date;
Frank
At 01:33 PM 4/01/00 -0500, you wrote:
>The table has a field called 'stname char(17)' which is indexed. The
>query is "SELECT * FROM data WHERE stname LIKE 'MAIN%'". I'm running on
>Redhat 6.1, 128MB ram, 40GB, P350. The actual index file is 4 MB.
I haven't tried it, but didn't someone mention a
select lo_date from payperiod;
lo_date
--
1999-12-16 00:00:00-05
1999-12-30 00:00:00-05
lo_date is defined as timestamp.
In PHP3 I retreive the rows and lo_date ends up in $row[2].
echo $row[2], date('D M-j',$row[2]), strftime('%a %b-%d',$row[2]);
yeilds
1999-12-16 00:00:00-05
13 matches
Mail list logo