If these people really work with hierarchically structured data, let
them try a hierarchical database (even though PostgreSQL is your
favourite database). They will profit 100fold from the advantages such a
database has for such data. I now several biologists specialized in
taxonomy (which is by na
On Wed, Apr 18, 2007 at 10:36:14AM -0700, RPK wrote:
> I have a table called "StudentFeesPayment" with columns "ReceiptNo" and
> "ReceiptMonthYear".
> The column, "ReceiptMonthYear" stores date in the format "-mm-dd". I
> have to find the max(ReceiptNo) where Month of (ReceiptMonthYear)=4. Or
>
Good day, Joe.
>> Table must be created in traditional way (by "create table, alter
>> table") and not through browser.
>> User must use "create table", etc in database-terminal like "psql.exe".
> By "in a special way" I meant that tables have referential constraints
> to other tables and they app
I'll continue with the analogy
It is not impossible to attach wings to a sportscar. When you do, you
will probably get the sportscar flying.
However:
1. Why would you even try, if airplanes (which are designed from
scratch to fly) already exist. Just use them
2. If you try nevertheless, is getting
Hi Dmitry,
On Mon, 2007-04-23 at 11:20 +0300, Dmitry Turin wrote:
> >I would change your examples to use less abstract
> > data, like department/employee, customer/product/order/order_line
>
> This will not help.
> To my mind, forum of real database is place,
"What we got here is ... failure to
I have a little Perl problem. When I call function dbi_select_test like
SELECT * from dbi_select_test() I get the expected result.
However when I call SELECT * from dbi_select I get an error message
saying "ERROR: error from Perl function: setof-composite-returning Perl
function must call return_
Dear Postgres folks;
I'm considering using a postgres table for something that could be done
with a flat file. Is this a good idea?
I have events on a machine "A", which need to be sent by an SMS/Cell
Phone modem that's on a totally different machine "B". Potentially this
is a job for a flat fi
If it's going to be too big for a database, then it's going to be worse
using flat-files on a disk :)
I'd suggest putting it in a database, and have 2 tables:
1) "New" messages to be sent
2) Archive messages
That way the polling machine only has to wait for the database to scan th
> But I'm thinking that maybe it's a job for a database table. Each
> new
> row would be written with a status (10="new"). And that the modem
> process would poll for new rows. Problem is there will be lots of
> rows,
> but only a trivial few will be "new". The huge index file and the
> pollin
