2010/8/7 Alban Hertroys dal...@solfertje.student.utwente.nl:
On 7 Aug 2010, at 5:19, Sandeep Srinivasa wrote:
+1 on this.
This is very interesting from the point-of-view of transitioning MySQL
webapps to Postgres. The truth is that for a lot of people, MySQL is their
first DB (because of
On Tue, May 18, 2010 at 2:12 PM, Charo Carino charo_car...@hotmail.com wrote:
- data stored in the database includes text, numbers, pictures and even
video clips
- avoids vendor 'lock ins' -- open DBMS
- allows for a web-based end (web 2.0)
- fully searchable by anyone from anywhere and
1. We have a production system tracking value added to a batch through
series of stages. Value table is updated through triggers on data
tables.
2. These trigger functions have been tested and validated for over 1.5
years with more than 100,000 records.
3. We found a difference in the
2010/4/23 Merlin Moncure mmonc...@gmail.com:
You haven't given enough information to make any sort of reasonable
diagnosis. Most people are going to assume the problem is on your end
but it's possible to know for sure without having the trigger function
at the very least.
Thanks merlin for
2010/4/23 Merlin Moncure mmonc...@gmail.com:
There's way too much logic going on there for me to test all the
different cases.
I suspect this is your problem: you triggered a case somehow which is
not handled properly via your labyrinth of switches and loops. I
highly doubt this is a case
Dear Friends,
I have loaded the backup from a live database in a test system. Both run
8.3.5 versions. The plan for a query varies in these systems.
Test System
A. PostgreSQL 8.3.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.2
20061115 (prerelease) (SUSE Linux)
B. explain select * from
Thanks a lot.
On Sun, Nov 30, 2008 at 11:28 PM, Tom Lane [EMAIL PROTECTED] wrote:
David Rowley [EMAIL PROTECTED] writes:
I assume workmem, effective_cache_size and random_page_cost are all the
same
in the 2 postgresql.conf?
Indeed, work_mem is probably the problem. The critical
On Sun, Nov 30, 2008 at 3:28 PM, David Rowley [EMAIL PROTECTED] wrote:
You might find this page interesting:
http://www.depesz.com/index.php/2008/08/13/nulls-vs-not-in/
Thanks David. Another issue I was faced with was exactly what the link you
provided discusses.
Best regards,
Ma Sivakumar
On Nov 15, 2007 8:17 PM, Sam Mason [EMAIL PROTECTED] wrote:
As Albe suggested, a view is about all that's going to help the poor
people who work with this. When I do this sort of thing, I tend to
find that there are very few queries that actually need everything all
together in one place.
On Nov 15, 2007 7:32 PM, Albe Laurenz [EMAIL PROTECTED] wrote:
You want to have a conditional foreign key reference that checks
against different tables depending on a type field, right?
For complicated conditions like this, you could use a
BEFORE INSERT trigger that throws an error when the
On Nov 15, 2007 5:52 PM, Sam Mason [EMAIL PROTECTED] wrote:
What I tend to do here, is something like:
CREATE TABLE test (
type INTEGER,
ref1 INTEGER REFERENCES table1 CHECK ((type = 1) = (ref1 IS NOT NULL)),
ref2 INTEGER REFERENCES table2 CHECK ((type = 2) = (ref2 IS NOT
Is there a way to force join conditions in queries i.e. When a join is
made to a table on a particular field, another column should also be
checked?
CREATE TABLE test (info_type varchar(3), info_reference integer);
(depending on info_type, info_reference will contain key values from
different
After upgrading to 8.2.4 version of PostgreSQL (Suse Linux, compiled from
source), function display in psql is changed.
In 8.1 version, using \df+ command we get the function description as
entered while creating it. In 8.2 version this seems to have changed. There
are additional characters and
13 matches
Mail list logo
