On Sun, 30 May 2004 22:08:10 +0200
Karsten Hilbert <[EMAIL PROTECTED]> wrote:
> > This then, removes the first part of my explanation, and dumps me
> > completely in the second part, which is where the biggest problems
> > reside.
> AFAICT 7.4 does much better error handling (no, you can't
> easil
On Sun, 30 May 2004 20:04:50 +0200
Karsten Hilbert <[EMAIL PROTECTED]> wrote:
> > a) The basic contents of the internal data dictionary can be used to
> > check incoming fields from on their length and permitted contents.
> >
> > b) With a little extra work, I should be able to define a table
> >
I am currently designing an application which should be accessible from
different interfaces. For this I like to be using stored procedures to
process the contents of form submissions and dialog screens.
After studying the PG database, it seems to me that I can fulfill the
following requirements.
On Sun, 30 May 2004 07:11:18 -0500
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> On Sun, May 30, 2004 at 12:18:05 +0200,
> Jurgen Defurne <[EMAIL PROTECTED]> wrote:
> >
> > Please do not reply or flame me for this.
> > --
> >
> >
Dear all,
I hope that my following question does not start a flamewar, but what
do you consider the most mature Python to postgreSQL interface, psycopg,
popy or pygresql ?
Regards,
Jurgen
---(end of broadcast)---
TIP 8: explain analyze is your fri
Dear all,
Is there a way to obtain more information about error messages, eg. the
name of the column which generates an error ?
I find it problematic that when some operations cause an error, there is
no feedback about the complete error, eg. when I do an INSERT into a
field, which exceeds the fi
Marcin Inkielman wrote:
> On Sat, 26 Aug 2000, Jurgen Defurne wrote:
>
> > Date: Sat, 26 Aug 2000 07:36:25 +0200
> > From: Jurgen Defurne <[EMAIL PROTECTED]>
> > To: Marcin Inkielman <[EMAIL PROTECTED]>
> > Cc: postgreSQL general mailing list <[EMAIL
Marcin Inkielman wrote:
> HI!
>
> I have such problem:
> Is the amount of tables limited in Postgresql7.0?
> Has anybody tried to use EFFECTIVELY a database
> with 1 tables at all?
>
> Thx for help.
Are you really sure you NEED a database with 1 tables ?
Jurgen
Patrick Welche wrote:
> On Tue, Jun 06, 2000 at 06:42:08PM +0200, Jurgen Defurne wrote:
> > A 'tuple' is an element of a set. A set is also called a table. When you do N
> > insertions on a table, then you get a table/set of N tuples. When you
> > query a table/
ructure in memory, and not write them to any table or
temporary file. Python has enough basic and extended datastructures to do
that.
If your tuplesize is 100 bytes and you are sure that you have a maximum
of 300 tuples, then you will spend approximately 30 Kb of memory (not
counting run-time overhead). Using a simple list to store your data
will simplify your life much, and you don't need to worry about memory
management.
Good luck.
Jurgen Defurne
[EMAIL PROTECTED]
ead, because your OS handles it directly.
Concerning the benchmarking, it seems as if the only way to do this is to
automatically start scripts which do what needs to be done and then
measure what happens : nr of processes, CPU and IO-load.
Jurgen Defurne
[EMAIL PROTECTED]
it.
BEGIN WORK;
-- Open cursors here
-- Work with cursors here
-- COMMIT or ROLLBACK, depending on the outcome of your program
Jurgen Defurne
[EMAIL PROTECTED]
s amount of analysts to reach a datamodel of 1M+
tables, or else it is based upon a large number of simple tables, in which
case it could be reduced in size.
I'm sorry, but my feeling is that 1M+ tables for a datamodel is preposterous.
Jurgen Defurne
[EMAIL PROTECTED]
, have you thought about the fact that more than one
person could have the same first and last names ? Do not confuse the
improbable with the impossible. When names are entered, you should check
how much results you have and probably show another screen on which
the user can select the right person.
Jurgen Defurne
[EMAIL PROTECTED]
cation and the database.
Good luck.
Jurgen Defurne
[EMAIL PROTECTED]
good,
you could probably write a similar interface to postgreSQL as is
used in CodeBase.
Good luck,
Jurgen Defurne
[EMAIL PROTECTED]
vironment like the above.
>
>
> (...little bit affraid)
>
> Marcel Sierra i Alegret
> from Barcelona
Jurgen Defurne
[EMAIL PROTECTED]
CYCLE option restarts the sequence automatically upon overflow. Of
course, your analysis of the database should point out that it is possible
to do this.
Jurgen Defurne
[EMAIL PROTECTED]
ase theory,
normalisation, writing applications in several languages : Tcl/Tk for
front-ends, PL/pgSQL for triggers and datamodel analysis.
Jurgen Defurne
[EMAIL PROTECTED]
ec $connection $query]
if {![string compare [pg_result $QResult -status]
"PGRES_COMMAND_OK"]} {
clear_fields
} else {
message .errorMsg -text [pg_result $QResult -error]
}
What you can do is wait for your pg_result status, if it says OK then
your front-end can issue
the message itself. No need to write complex codings in a trigger.
Jurgen Defurne
[EMAIL PROTECTED]
-plug capabilities, it is
possible to keep the system running either if a CPU goes down or if a
drive fails.
The worst thing that you can do is to base the implementation of your
application upon the fact that the system should have high-availability
requirements. That is not a database issue, b
o master myself.
Regards,
Jurgen Defurne
Flanders
Belgium
ss 0.98
is nice to create and view tables, but there are still many things which
need to be implemented.
Regards,
Jurgen Defurne
Flanders
Belgium
University College of the Cariboo
> ... [EMAIL PROTECTED]
> .. http://www.ocis.net/~jcl
> .
>
> The Search for Extraterrestrial Intelligence from Home:
> http://setiathome.ssl.berkeley.edu
>
> LINUX!
>
>
Jurgen Defurne
Flanders
Belgium
24 matches
Mail list logo
