Hello everyone,
I'm just beginning a PHP / PostgreSQL project for someone and there are a
couple of things where I am not sure the best design for the database.
The first is that we want to store kind of a history of values for the past
3 days or so. We want to use this so that we can analyze
> "Randall" == Randall Parker <[EMAIL PROTECTED]> writes:
Randall> The title says it all: Is this a foolhardy or prudent and
Randall> wise move at this time? Has anyone run Postgres
Randall> databases on ReiserFS volumes under heavy enough load and
Randall> for long enough to
At 09:34 7/07/00 -0300, The Hermit Hacker wrote:
>
>am investigating this right now ...
>
>On Fri, 7 Jul 2000, Thomas Lockhart wrote:
>
>> > Now, a) is easily fixable by just extending the date to 2000, but that
>> > still only covers "UNIVERSITY OF CALIFORNIA", and none of the actual
>> > develop
> > I just didn't implement the corresponding "year" code at least partly
> > because I wasn't sure what to call it. 'iyear' seems like a pretty good
> > choice, or should it be 'isoyear'? 'year' is already used, obviously,
> > and if 'iyear' is chosen then perhaps I should change 'week' to 'iweek
Hi all,
I have created a database that reliably crashes postgresql when i try a
insert/update on one table but not another. Even when I pg_dump the db
and reload it on a new machine/new db it still crashes. I'm not exactly
sure whats up here...
I'll submit a proper bug request, but I'd like t
Actually, you should (hopefully) be able to drop
t2. That is supposed to remove the constraints
referencing it (technically speaking drop table is
probably supposed to take an argument to
determine whether to do this, but we don't yet).
If it's actually failing for you, can you give us a
copy o
Camm Maguire writes:
> As would mine. The major cost associated with any software project is
> the migration/learning curve time. Effective guarantees that this
> time investment will have a long payoff period (i.e. there will be no
> forced upgrades, mandatory incompatibilities, binary/linked
On Thu, Jul 06, 2000 at 12:21:31PM +0200, Robert wrote:
> - each client gets separate database
>
> - one common database for all clients, each table has client_id field
> added
I'm not in your situation, but I can tell you that if you went with method
two, I would not recommend your services to m
thanks, i just discovered that before i got your message.
now that i have that shovel, maybe i should whack myself
with it!!! :)
thanks again,
mikeo
At 02:34 PM 7/7/00 -0400, Tom Lane wrote:
>mikeo <[EMAIL PROTECTED]> writes:
>> hi, i accidently deleted a foreign key trigger from pg_trigger
>
mikeo <[EMAIL PROTECTED]> writes:
> hi, i accidently deleted a foreign key trigger from pg_trigger
Did you reach into pg_trigger and delete the record yourself, or did
a system bug cause the problem?
> and now cannot get at the table. i get the message:
> ERROR: RelationBuildTriggers: 1 record
Hello,
We are using a postgresql-7.0.2. Consider the following
scenario
we have created a table t1 with columns
c1 : having referential integrity with
t2.c1
c2 : having referential integrity with
t3.c2
where t2 and t3 are different tables
Assume that t2 has also got a referent
hi, i accidently deleted a foreign key trigger from pg_trigger
and now cannot get at the table. i get the message:
ERROR: RelationBuildTriggers: 1 record(s) not found for rel feature_code
can anyone give me a shovel :)
or a little help to get out of this please?
TIA,
mikeo
With PostgreSQL is there any way to have encrypted connections to the database?
Also, once the SSL patent expires in Sept or Oct of this year has any thought been
given to SSL support? Could one easily
implement this by picking up the source to the OpenBSD package that is for this
purpose? The
Steve Heaven <[EMAIL PROTECTED]> writes:
> We run 6.5.2 on a Mandrake Linux 6.1 box.
> The scripts create various temporary tables which are then later
> dropped. Occasionally the 'DROP' doesnt work properly. The file
> base// gets deleted, but the entry in pg_class
> doesnt. This leads to a tabl
I have a set of tables and some views which perform calculations on
those table to which no one except the group officestaff has
any permissions. No problem.
I tried to create views to which some particular client would have
permissions. These views would be filtered versions of the private vie
On Fri, 7 Jul 2000, Thomas Lockhart wrote:
> > > ISO-week: week that has more than 4 day and start in Sunday.
> > What about weeks that start in Monday (as here in Norway)?
>
> You can probably calculate that from the existing date/time code. But it
> isn't ISO-8601. Karel was referring to the
> Now, a) is easily fixable by just extending the date to 2000, but that
> still only covers "UNIVERSITY OF CALIFORNIA", and none of the actual
> developers ...
afaik we can't unilaterally alter the original license, either for dates
or for participants. However, we can send along a second licens
On Thu, 6 Jul 2000, Helge Haugland wrote:
> On Thu, Jul 06, 2000 at 15:21:53 +0200, Karel Zak wrote:
> > ISO-week: week that has more than 4 day and start in Sunday.
>
> What about weeks that start in Monday (as here in Norway)?
Yes, I known, in my country too. A question is how discern it -
18 matches
Mail list logo