On Nov 4, 2005, at 2:58 , zackchandler wrote:
The problem is I am very concerned about scalability with having a
different
table created for each custom object. I want to design to site to
handle
tens of thousands of users. If each user has 3-5 custom objects the
database would have to ha
Hi everybody. Quick question:
I'm designing an application that will allow users to create custom objects
on the application level. A custom object can have zero or more attributes.
Attributes can be one of 5-10 types (ex. String, Number, List, Date, Time,
Currency, etc...). This will allow user
Hi,
I am wondering if there is a way to set conditions on a left joined
table without hosing the join altogether:
query = qq |SELECT p.*, a.user_id
FROM patient_dosing p
LEFT JOIN patient_assignment a
ON p.patient_id = a.patient_id
WHERE p.dose_
I have two queries that return the same results, but one is 6 times
slower than the other one, can anyone enlighten me as to why?
My initial guess is that it is not able to utilize the index on
foo.tracktitle to sort the result set after foo has been joined with
other tables. This seems kind of br
Hi,
What function should I use to get a serial number, together with my results,
from a query?
Ex. Of output I want:
1 ooo pp ij
2 hou joo iu
3 bhi ft yh
Basically, I would like to have one column with integers, from 1 onwards, no
matter how man
On Nov 4, 2005, at 1:17 , Judith Altamirano Figueroa wrote:
Hi everybody, in Postgres 7.0.2 I have the next query:
SELECT * from clientes_proceso where fecha_mod::date <= now() -1;
but in version 8.0.1 returns the next error:
ERROR: The operator doesn't exist: timestamp with time zone - inte
Quoting Judith Altamirano Figueroa <[EMAIL PROTECTED]>:
Hi everybody, in Postgres 7.0.2 I have the next query:
SELECT * from clientes_proceso where fecha_mod::date <= now() -1;
but in version 8.0.1 returns the next error:
ERROR: The operator doesn't exist: timestamp with time zone - integer
How c
Hi everybody, in Postgres 7.0.2 I have the next query:
SELECT * from clientes_proceso where fecha_mod::date <= now() -1;
but in version 8.0.1 returns the next error:
ERROR: The operator doesn't exist: timestamp with time zone - integer
How can drop a day to now()??
I recently upgraded my DB from 7.4.3 to 8.0.4 and I've noticed the following errors appearing in my serverlog:
2005-11-03 05:56:57 CST 127.0.0.1(38858) ERROR: Unicode characters greater than or equal to 0x1 are not supported
2005-11-03 06:04:09 CST 127.0.0.1(38954) ERROR: invalid byte seque
Mario Splivalo <[EMAIL PROTECTED]> writes:
> SELECT *
> FROM messages
> WHERE (id = currval(''public.message_id_seq''::text))
That cannot legally be converted into an indexscan, because currval() is
a volatile function --- the planner cannot be certain that its value
won
For some reason i got unsubscribed from sql
for no apparent reason.
(I cant recall anything close to that,
and i never intented to unsubscribe from -sql list)
The [EMAIL PROTECTED] person might be
interested in investigating this.
Thank you.
--
-Achilleus
---(end of
I have a procedure that goes something like this:
-- Function: create_message(varchar, varchar, varchar, int4)
-- DROP FUNCTION create_message("varchar", "varchar", "varchar", int4);
CREATE OR REPLACE FUNCTION create_message("varchar", "varchar",
"varchar", int4)
RETURNS SETOF messages AS
'
DECL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.11.2005 um 00:22 schrieb Tom Lane:
Axel Rau <[EMAIL PROTECTED]> writes:
Question: Can rtree_inet be included in the core?
No, because rtree is going away in 8.2. Feel like converting that
code to be a GIST opclass, instead?
Perhaps. It wo
13 matches
Mail list logo
