-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 15:53, Jan Muszynski wrote:
> Rather simple question, of which I'm not sure of the answer.
>
> If I have a multiple column index, say:
> Index index1 on tableA (foo,bar)
>
> and I then:
> Select * from "tableA" where foo =
>
> W
aster
> depending on the number of different values/combinations, so probably
> "it depends" eh?
>
>
> On Fri, 19 Jan 2007 16:57:42 -0600, "Ron Johnson"
> <[EMAIL PROTECTED]> said:
> On 01/19/07 15:53, Jan Muszynski wrote:
>>>> Rather simp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 18:21, Bruce Momjian wrote:
> Sorry, I know of no way to get a status bar that shows how far the an
> INSERT or COPY has progressed. People have asked for it, but no one has
> any idea how to implement it.
How hard *would* it be to patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/07 10:52, Bruce Momjian wrote:
> Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 01/19/07 18:21, Bruce Momjian wrote:
>>> Sorry, I know of no way to get a status bar that sho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/07 16:52, Michael Nolan wrote:
> I have a MySQL table on our public website that is populated from a similar
> table on our internal site, which runs PostgreSQL.
>
> Recently I was trying to enhance one of our website queries and ran across
>
lightly lazy programming on my part, but it makes little difference in
> either PostgreSQL or MySQL whether I use = or 'in'.
> --
> Mike Nolan
>
> On 1/20/07, Ron Johnson <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> Is this query created by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/07 10:20, Joshua D. Drake wrote:
> Shashank wrote:
[snip]
>> Where is this announcement? They don't need to drop either
>> engine, as both are GPL. MySQL as a group was never too hot
>> with BDB.
>
>
> http://www.linux.com/article.pl?sid=06/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 03:43, Alban Hertroys wrote:
> Paul Lambert wrote:
>> G'day folks,
>>
>> I'm faily new to the world of Postgre so excuse me if these
>> questions seem ignorant.
>>
>> My current employer develops a software package which runs on
>> OpenVM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 07:09, Paul Lambert wrote:
>
> Alban Hertroys wrote:
>> Paul Lambert wrote:
>>
[snip]
> I'd imagine there aren't too many VMS programmers around that
> would be willing to port Postgres either, but if anyone out there
> with experience in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 08:22, Martijn van Oosterhout wrote:
> On Mon, Jan 22, 2007 at 04:10:15PM +0200, Sim Zacks wrote:
>> How good is postgresql security?
>
> Good, within limits.
>
>> For example, If I have data that I do not anyone to see, including the
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 05:49, Peter Rosenthal wrote:
> Right,
>
> You also have to realize that your first query might return zero results,
> and MySQL (and maybe this is correct SQL behavior) balks at an empty value
> set "where table_id in ()".
>
> I would ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 09:55, Jan Muszynski wrote:
> On 22 Jan 2007 at 16:10, Sim Zacks wrote:
>
>> How good is postgresql security? For example, If I have data
>> that I do not anyone to see, including the programmer/dba, is
>> it enough to change the password
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 14:01, Paul Lambert wrote:
> Ron Johnson wrote: On 01/22/07 07:09, Paul Lambert wrote:
>
>>>> Alban Hertroys wrote:
>>>>
>>>>> Paul Lambert wrote:
>>>>>
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 16:55, Bruce Momjian wrote:
> Engada wrote:
[snip]
> When we got the PostgreSQL code from Berkely, it had code that
> supposedly ran on VMS (not OpenVMS), but no one was available to
> maintain it, so eventually it was removed.
DEC Marketi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/07 17:22, Robert Sanford wrote:
> It appears to me that there is some inconsistency in the date
> calculations for my PostgreSQL install (version 8.0 on Win32).
>
> January 07 of 2007 is a Sunday. Based on the documentation I would
> expect t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/07 13:06, guillermo arias wrote:
> Hello, i am Guillermo Arias, from Peru. I have a doubt about
> capacity of tables. I am developing a software for accountants,
> and my principal problem is about the table for the vouchers. I
> have to decid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:30, Inoqulath wrote:
> Hello Folks
>
> Have a look at this Table:
>
> CREATE TABLE foo(
> id serial,
> a_name text,
> CONSTRAINT un_name UNIQUE (a_name));
>
> Obviously, inserting a string twice results in an error (as one would
> exp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:34, Isaac Ben wrote:
> Hi,
> I'm trying to create a table with 20,000 columns of type int2, but I
> keep getting the error message that the limit is 1600. According to
> this message
> http://archives.postgresql.org/pgsql-admin/2001-01/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:45, Thorsten Körner wrote:
> Hi,
>
> when I fire the following query:
> select m_id, m_u_id, m_title, m_rating from tablename where m_id in (26250,
> 11042, 16279, 42197, 672089);
>
> I will get the same results in the same order, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:54, [EMAIL PROTECTED] wrote:
> Ron Johnson wrote:
>> On 01/25/07 09:30, Inoqulath wrote:
[snip]
> I think he is not asking "How do I insert duplicate rows into a
> unique-constrained column?", but rather that he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 15:43, Bill Moran wrote:
> In response to Mark Drago <[EMAIL PROTECTED]>:
[snip]
> I don't think either of those are good ideas, because they both
> rely on disk limits to trigger drastic changes in database size,
> which will then require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 13:37, Isaac Ben wrote:
> On 1/26/07, Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>> On Thu, Jan 25, 2007 at 10:47:50 -0700, Isaac Ben
>> <[EMAIL PROTECTED]> wrote:
[snip]
>
> I plan on accessing the data with postgres via python and R. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 17:28, Shane Ambler wrote:
> Bill Moran wrote:
>> I spend some time googling this and searching the Postgresql.org site,
>> but
>> I'm either not good enough with the search strings, or it's not to be
>> found.
>>
>> I'm trying to plan upgr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 20:12, Bruce Momjian wrote:
> Ron Johnson wrote:
>>> There is no set time frame planned that I know of.
>>>
>>> It is more a matter of users that keep the old versions alive. Some with
>>> large datas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 21:48, Bruce Momjian wrote:
> Ron Johnson wrote:
>>> Yes:
>>>
>>> http://www.postgresql.org/docs/8.2/static/migration.html
>> I was thinking of something like the release notes, but a bit more
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 00:19, Martijn van Oosterhout wrote:
> On Fri, Jan 26, 2007 at 10:16:39PM -0600, Ron Johnson wrote:
>> What are your plans for reducing the number of resources needed to
>> upgrade databases?
>
> As noted, the table s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 04:13, Anton Melser wrote:
> On 26/01/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
>> On Jan 25, 2007, at 12:47 PM, Benjamin Smith wrote:
>> > On Tuesday 23 January 2007 13:55, Carlos wrote:
>> >> What would be the faster way to convert a 7.4.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 11:50, Bill Moran wrote:
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
>> Devrim GUNDUZ wrote:
[snip]
> Of course, the end of "official" support for a project doesn't prevent folks
> with an interest from continuing to support it unofficially.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 08:36, John Meyer wrote:
> Joris Dobbelsteen wrote:
>>> CREATE TABLE attendance
>>> (
>>> attendanceid serial primary key,
>> Why you have this??? You already have (entered,timeperiod,studentid)
>> that you can use, since that must be uniq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 07:05, garry saddington wrote:
> I have a table definition such as:
>
> CREATE TABLE attendance
> (
> attendanceid serial primary key,
> entered date DEFAULT current_date NOT NULL,
> absent boolean,
> authorization text default 'N'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
These fields do not use any disk space, as the data in them is
derived on the fly.
For example:
CREATE TABLE T_EXAMPLE (
SOME_DATE DATE,
JDATE COMPUTED BY EXTRACT(JULIAN FROM SOME_DATE)
);
A work-around is to create a function, and reference
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 10:43, A. Kretschmer wrote:
> am Sun, dem 28.01.2007, um 10:25:33 -0600 mailte Ron Johnson folgendes:
>> Hi.
>>
>> These fields do not use any disk space, as the data in them is
>> derived on the fly.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 15:18, garry saddington wrote:
> On Sun, 2007-01-28 at 09:57 -0600, Ron Johnson wrote:
>> On 01/28/07 07:05, garry saddington wrote:
[snip]
>> When you say "certain days", you mean "days of the week&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/07 13:20, Vivek Khera wrote:
>
> On Jan 27, 2007, at 10:45 AM, Ron Johnson wrote:
>
>> Using slony or "piped pg_dump" requires that you have *double* the
>> amount of disk space. Having a *very large* dat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/07 16:05, tom wrote:
> No.
> Postgres does not represent an economic entity that can compete for $$
> with Oracle.
>
> It's also not nearly as popular. And I mean that in a very pop-culture
> way.
> How long did it take Oracle to support Lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 00:32, Hakan Kocaman wrote:
> Hi,
>
> you can find a nice virtual folder implementation in the
> Opera-Mailclient M2. Not sure if this also works with IMAP (don't
> use IMAP yet).
>
> Virtual folders are based on regexes over various fiel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 13:33, Brandon Aiken wrote:
> I always assumed the general argument is if you need to query different
> databases on the same server with the same application, they ought not
> to be separate databases because they're clearly related data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 14:41, Tony Caduto wrote:
> Mark Walker wrote:
>> It's sort of a matter of taste, but there are lots of people who like
>> to keep there logic on the server or at least within sql statements,
>> so there's probably a good sized market that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 14:50, Rich Shepard wrote:
> On Tue, 30 Jan 2007, Mark Walker wrote:
>
[snip]
> At last year's at O'Reilly's OSCON here in Portland I had this discussion
> with the booth babes sales droids from Sugar-CRM. They said that they heard
> num
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 15:55, Richard Troy wrote:
>> On 01/30/07 14:41, Tony Caduto wrote:
>>> Mark Walker wrote:
[snip]
> These days with good open source choices, things are a bit
> different, but that doesn't mean it's always good to go hog wild
> with any par
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 16:35, Mark Walker wrote:
> LOL, I remember those days. "Uh, can you hold on? My computer just
> went down." or "you need to fill out form 1203-B, send us $25 and we'll
> get you the information you need in six weeks." Just kidding, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 23:46, Paul Lambert wrote:
> Richard Troy wrote:
>>
>> [snip] My observation is that we have a real shortage of
>> quality
[snip]
>> Meanwhile, what Operating Systems ARE _today_ reliable choices
>> upon which to run your Postgres databab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/07 12:37, Jeff Davis wrote:
> On Tue, 2007-01-30 at 20:44 -0800, David Fetter wrote:
>> On Tue, Jan 30, 2007 at 04:43:14PM -0800, Richard Troy wrote:
>>> On Tue, 30 Jan 2007, Mark Walker wrote:
I don't know. My customers expect 24/7 reli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/07 20:00, Paul Lambert wrote:
> Mark Walker wrote:
>> One other thing. Another approach to this problem would be to have
>> some sort of code signing/authentication capabilities for the
>> postgresql server. For instance, you login as an adm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 03:02, roopa perumalraja wrote:
> Hi all,
>
> While there are inserts & updates happening into the database, is
> it possible to make the base backup without losing any of the
> updates in the database?
pg_dump does transactionaly-consist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 15:15, Richard Troy wrote:
> Hello All,
>
> it was recently brought to my attention that last year the U.S. altered
> the dates when Daylight Savings Time starts and ends. Many if not most
> computers presume the old change dates and there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 16:27, Glen Parker wrote:
>> Open-database file-level backups might work with PITR, but I
>> wouldn't trust it.
>
> IME, it does work, and very well. Inconsistencies in the heap files are
> trumped by the WAL archive during recovery.
Tar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 18:04, Glen Parker wrote:
>> Tarring hot database files still gives me the willies. But then, I
>> wear belt and suspenders.
>
> I understand. A list of "file changed while we read it" errors is just
> a little unnerving at first!
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 19:02, Jim C. wrote:
> I've a postgres statement that reads:
>
> CREATE TABLE "channel" (
Do you *need* object names to be case-sensitive?
If not, it's a bad habit to get in to. Makes more work for you and
the developers.
> "chan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 21:31, RPK wrote:
> How is FireBird rated when compared with PostgreSQL?
Rated?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFwrSGS9HxQb37XmcRAj+lAJ9uFM+hNm+ink5SeOaaNRjCuASMaACgiBeE
PmhLjdXNwlPKRHHYpGuK+c4=
=v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/07 06:01, Tomi N/A wrote:
> I'm trying to set up an automatic backup mechanism and have a number
> of questions about issues I've encountered.
> First of all, I tried to install pgAgent (the server is running win2k3
> and pgsql 8.1.5). Trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/07 07:22, Richard Huxton wrote:
> Peter wrote:
>>
>> Query returned successfully with no result in 600 ms.
>>
>> Why SELECT takes 3+ second to execute? Is it something to do with my
>> Postgres server optimization, or PgAdmin does not show cor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 21:14, Jim Nasby wrote:
> On Jan 27, 2007, at 10:45 AM, Ron Johnson wrote:
>> Using slony or "piped pg_dump" requires that you have *double* the
>> amount of disk space. Having a *very large* database and double
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/07 12:07, Lincoln Yeoh wrote:
> At 09:36 AM 2/2/2007, Ron Johnson wrote:
>> >
>> > OTOH, I still take a full base backup every night and keep ten days
>> > worth of WAL files on our backup server, so I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/07 07:17, Tom Allison wrote:
> Alban Hertroys wrote:
>> Jean-Gérard Pailloncy wrote:
[snip]
> The *one* feature I did like about dspam is they quarantine spam and you
> can sort it out later. That can be done easily enough and won't
> interfe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/07 09:48, Jamie wrote:
> I typically use compound primary keys when creating a table that
> represents a many-to-many relationship. I was wondering if anyone else
> had other situations in which you would use a compound PK? Why do you
> use it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/07 10:59, Scott Marlowe wrote:
> On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
[snip]
>> It's been said a million times by BSD advocats: put one line of code
>> under GPL and you instantly become a willingless slave of Richard
>> Stallman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/07 14:51, Scott Marlowe wrote:
> On Tue, 2007-02-06 at 11:59, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 02/06/07 10:59, Scott Marlowe wrote:
>>> On Tue, 2007-02-06 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/08/07 20:50, Arturo Perez wrote:
> Hi all,
>
> Saturday I changed a table to add a varchar(24) and a TEXT column. It's
> used for some reporting purposes (small potatoe stuff really) and the
> TEXT column remains mostly empty. However, this we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/07 07:46, Dmitriy Chumack wrote:
> Hi *
>
> I need to write a function, that returns a set of all columns from 2
> tables.
[snip]
> for i in select * from "Table1", "Table2"
> loop
>return next i;
> end loop;
[snip]
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/07 07:46, Ray Bannon wrote:
> I have a query which is running a bit slowly, and I'm wondering if anyone
> has a design improvement. Basically it's a series of unions as follows:
>
> Select ID, plan_name from table/view
> Where plan_name = 'A'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/07 07:54, filippo wrote:
> Hello,
>
> my database is not very big so I want to adopt this backup strategy:
>
> I want to clone my database every 1 hour to another
> database 'currenttime_mydatabase' in order to have 24 backup a day,
> overw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 01:36, A. Kretschmer wrote:
> am Tue, dem 13.02.2007, um 13:56:15 -0800 mailte vanessa folgendes:
>> hi guys,
>> i was just wondering if it was at all possible to turn a year and a given
>> week number into a real date just using postgresq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 01:42, Tom Lane wrote:
> Mike Harding <[EMAIL PROTECTED]> writes:
>> Where does that extra 8 hours come from?
>
> Ellay is 8 hours west of UTC (at least on 1-Jan, at least till our
> congresscritters see fit to monkey with the DST laws aga
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 02:13, A. Kretschmer wrote:
> am Wed, dem 14.02.2007, um 2:01:09 -0600 mailte Ron Johnson folgendes:
>>>> i was just wondering if it was at all possible to turn a year and a given
>>>> week number into a real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 02:52, A. Kretschmer wrote:
> am Tue, dem 13.02.2007, um 13:56:15 -0800 mailte vanessa folgendes:
[snip]
>
> test=*# select get_week(2007,2);
> get_week
> -
> 08-01-2007 - 14-01-2007
> (1 row)
Is that wee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 03:33, A. Kretschmer wrote:
> am Wed, dem 14.02.2007, um 3:10:17 -0600 mailte Ron Johnson folgendes:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 02/14/07 02:52, A. Kretschmer wrote:
>>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 12:41, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
>> On Tue, 2007-02-13 at 07:54, filippo wrote:
>>> my database is not very big so I want to adopt this backup strategy:
>>> I want to clone my database every 1 hour to anot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 13:40, Ted Byers wrote:
>> Maybe his real goal "all the backups readily available to be read by
>> my program (opening the backup read only)" is to have a historical
>> record of what certain records looked like in the past.
>>
>> There are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 14:59, John D. Burger wrote:
> With a slip of the keyboard, I just dropped a database I'd like to have
> back. I don't have PITR or anything turned on - if nothing else has
And no backups?
> been done to the cluster since then, is there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 19:11, carter ck wrote:
> Hi all,
>
> I am looking for ways to create an archive of records older than 3
> months in one of my table, and store these extracted records into a
> local database. Does Postgres have any command to do this?
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 19:34, Paul Lambert wrote:
> Ron Johnson wrote:
> On 02/14/07 19:11, carter ck wrote:
>>>> Hi all,
>>>>
>>>> I am looking for ways to create an archive of records older than 3
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/07 02:29, RPK wrote:
> Is there any option in PGSQL to undo last changes done on a table?
Presumably, this is *after* you committed them?
> Any
> feature similar to "FlashBack Query" in Oracle.
>
-BEGIN PGP SIGNATURE-
Version: GnuP
of PLAN_NAME values in it
would also work, but then you'd have to join the lookup table to
SOME_TABLE on PLAN_NAME.
> On 2/13/07 11:29 PM, in article [EMAIL PROTECTED], "Ron Johnson"
> <[EMAIL PROTECTED]> wrote:
>
> On 02/13/07 07:46, Ray Bannon wrote:
>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 01:14, filippo wrote:
> On 13 Feb, 14:54, "filippo" <[EMAIL PROTECTED]> wrote:
>
>> My target is to have the backup operation not affecting the users, so
>> I want to be able to copy a database even if the database is used by
>> someone.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/07 15:29, Guido Neitzer wrote:
> Am 15.02.2007 um 11:21 schrieb Marc Evans:
>
>> http://us.devloop.org.uk/
>
> These *peeep* [deleted] compared MySQL with MyISAM to ACID compliant
> databases. So why not compare an F-15 to 747? What?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/07 15:13, Bjørn T Johansen wrote:
> I have a table that I want to find rows that have the same value
> in two fields, e.g. all rows that have the same date and also the
> same productionid... How do I write such an sql statement?
If I unders
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/07 20:59, vanessa wrote:
> Hello!
> Does anyone have any idea about how to append the contents of a table to a
> file?
psql will do the what you asked in this question, but you are
probably needing more than you ask. If so, C, Python & Perl
Y SOME_DATE, PRODUCTIONID
HAVING COUNT(*) > 1;
>
> BTJ
>
> On Thu, 15 Feb 2007 16:46:21 -0600
> Ron Johnson <[EMAIL PROTECTED]> wrote:
>
> On 02/15/07 15:13, Bjørn T Johansen wrote:
>>>> I have a table that I want to find rows that have the same value
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/07 17:25, Chris Browne wrote:
> [EMAIL PROTECTED] (Vladimir Zelinski) writes:
>> I tried function now(),current_timestamp() but all of
>> them behave similar.
>>
>> I don't believe that it's bug, probably it's a feature
>> of the postgreSql da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/07 15:25, gustavo halperin wrote:
> Hello
>
> I have a friend that ask me why postgresql is better than mysql.
> I personally prefer posgresql, but she need to give in her work 3 or 4
> strong reasons for that. I mean not to much technical
x27;);
> ERROR 1292 (22007): Incorrect date value: '35-Feb-2007' for column 'td'
> at row 1
> mysql> select version();
> +-+
> | version() |
> +-+
> | 5.0.27-standard |
> +-+
> 1 row in set (0.00 se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/21/07 08:42, Michael Fuhr wrote:
> On Wed, Feb 21, 2007 at 08:54:30AM -0500, Jan de Visser wrote:
>> It gets better: The problem is not just feb 35, it's also that it doesn't
>> warn
>> you that it didn't like the input format:
>
> Actually it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/21/07 18:09, Erick Papadakis wrote:
> How would you like to use a database that has nuances like these --
> http://forums.mysql.com/read.php?20,141120,141120#msg-141120
Huh?
A blank string (does that mean '' or ' '?) is not NULL, so of
*course*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/21/07 19:01, Brusser, Michael wrote:
>
>>> How would you like to use a database that has nuances like these --
>>> http://forums.mysql.com/read.php?20,141120,141120#msg-141120
>
> ---
>
>> Huh?
>> A blank string (does that mean '' or ' '?) i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My definition is, "toy used/trumpeted by pseudo-professionals as a
professional tool, when it just doesn't measure up".
On 02/22/07 02:08, Tyarli wrote:
> he he. what does "the PHP of databases" mean?
>
> Joshua D. Drake wrote:
>> John Smith wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/07 10:40, Joshua D. Drake wrote:
>>> Well no. PHP is not a professional language because it has no really
>>> design - and that has nothing to do with the fact it beeing a scripting
>>> language. Its a bad scripting language. (Say namespaces f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/07 17:17, Jim Nasby wrote:
> On Feb 21, 2007, at 10:26 AM, Scott Marlowe wrote:
>> The only thing I can think of that rewrites a whole postgresql table
>> would be reindexing it, or an update without a where clause (or a where
>> clause that i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/07 19:04, Mark Walker wrote:
> I'm not sure what you're trying to do but, it appears that you database
> design is incorrect. What you need is something like
>
> CREATE TABLE temp_readings
> (
> _date Date,
> temperature double,
> source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/07 15:47, Peter Eisentraut wrote:
> Brandon Aiken wrote:
>> That's why you make a table for every device or every measurement,
>> and then use a view to consolidate it. With updatable views, there's
>> no excuse not to.
>
> No, you put them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/07 20:35, Martin Winsler wrote:
> I hope this isn't too far off topic. I've noticed some
> discussion about referential integrity, the use of nulls, and
> database design recently here. This is a real world situation
> where referential inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/24/07 11:00, Tom Lane wrote:
> "Tomi N/A" <[EMAIL PROTECTED]> writes:
>> ...which made me think: postgresql aims at the same (or very similar)
>> clients and use cases as Oracle, DB2 and MSSQL. I pose the question
>> from an advocacy standpoint:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/07 01:39, Karl O. Pinc wrote:
>
> On 02/25/2007 06:21:45 PM, Kenneth Downs wrote:
>> Martin Winsler wrote:
>
[snip]
> The above proposal takes care of the data
> structure/referential integrity
> issues, but does not solve the data integrity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/07 10:35, Filipe Fernandes wrote:
> [snip]
Martin Winsler wrote:
> Does anybody have any experience or knowledge of building
> financial accounting databases?
> [snip]
>
> I too was thinking about building a double entry accounti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/27/07 13:26, Dhaval Shah wrote:
> I am planning to use 8.2 and the average inserts/deletes and updates
> across all tables is moderate. That is, it is a moderate sized
> database with moderate usage of tables.
Moderate?
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/07 00:16, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>> In some databases if you know that an index just happens to be unique
>> you might gain some query performance by defining the index as unique,
>> but I don't think the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/07 10:31, Joshua D. Drake wrote:
I would imagine that other DBMSes also enforce uniqueness by means of
indexes, because it'd be awful darn expensive to enforce the constraint
without one; but I'm only guessing here, not having l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/27/07 01:04, mobil wrote:
> Is there a downlaodable high school database in postgresql
What exactly do you mean by "high school database"?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF5wuFS9HxQb37XmcRAk8OAKCEKRtzaX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/07 16:09, Charlie Clark wrote:
> Hi,
>
> I'm getting unexpected results on a query which involves joining two
> tables on two common variables (firstname and lastname).
>
> This is the basic query:
>
> SELECT table1.lastname, table1.firstna
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/07 20:38, Kenneth Downs wrote:
[snip]
> Management and we are about to add the CRM to it so that the
> scheduling/billing database also serves the doctor's public website,
Is that wise? One bug and a cracker is poking around some very
privat
301 - 400 of 637 matches
Mail list logo
