Hi Kris,
i am using Postgres 7.4.2 with jdbc. Every time i try to select a
varchar the SQL generated by the jdbc driver uses RTRIM(t0.columnname)
which breaks an existing application. Is this normal, can we disable
the RTRIM usage?
I assume from this bold claim that you have written an SQL query
Bruce Momjian [EMAIL PROTECTED] writes:
JM wrote:
Would a battery backed Card do the trick?
No because the fsync causes the data to hit the card. Without the
fscync, the data could remain only in the kernel cache.
A battery backed card for the transaction logs wouldn't make it safe to
Hello,
I know that the SQL norm contains some views to describes the tables (and
probably some other things) of a database.
Does PostgreSQL implement theses views (from which version number) ? I don't
find anything in the documentation about that.
Thanks in advance !
On Mon, 17 May 2004 09:32:49 +0200, Bruno BAGUETTE wrote:
I know that the SQL norm contains some views to describes the tables (and
probably some other things) of a database.
Does PostgreSQL implement theses views (from which version number) ? I
don't find anything in the documentation
Bruno BAGUETTE wrote:
Hello,
I know that the SQL norm contains some views to describes the tables (and
probably some other things) of a database.
Does PostgreSQL implement theses views (from which version number) ? I don't
find anything in the documentation about that.
You meant this?
Scot L. Harris wrote:
Currently using Postgresql 7.2.4-5.80 with php 4.2.2.-8.0.8 on a redhat
8.0 system.
I am writing some php scripts where I want to generate a list of the
column names in a particular table that the user selects. I could take
the brute force method and hard code the column
Hi,
today I started to wonder about type conversion. I want to get all rows
of a table dated between two given dates. Until now I use
select * from mytable where to_date('20040115', 'MMDD') = timestamp
and timestamp = to_date('20040215', MMDD')
Does that query include the 15th January as
I have a serial autoincrement column called idmember in my main table
(members). This serial column is a key to a second table. A row in
members table corresponds to many rows in the second table.
What is the best way to discover current idmember value if I create a
few rows in the second
Nikola Milutinovic wrote:
+ #define NAN DBL_INFINITY
The compilation has went smoothly, I'll try to run regression tests.
Will let you know if something fails.
Hate to reply to myself, but here goes.
With NAN defined as DBL_INFINITY I get 3 failed regression test, most
notably float8 test.
On 17/05/2004 11:24 Milos Prudek wrote:
Cmd = INSERT INTO members ... VALUES (...);
If you want PostgreSQL to populate your idmember field with the next value
from the sequence, you need to specify the keyword DEFAULT as its value or
omit it from the INSERT list of coulumns (this assumes you
If you want PostgreSQL to populate your idmember field with the next
value from the sequence, you need to specify the keyword DEFAULT as its
value or omit it from the INSERT list of coulumns (this assumes you have
I do omit it.
DEFAULT nextval('members_idmember_seq') defined on the idmember
Milos Prudek wrote:
I have a serial autoincrement column called idmember in my main table
(members). This serial column is a key to a second table. A row in
members table corresponds to many rows in the second table.
My question is: is this the best practice?
Here's an example in Python:
Alternatively, you could rewrite this query:
INSERT INO msg (idmember,txt) VALUES (currval('members_idmember_seq'),
%s);
Cool. You helped me demolish 3 lines of code with no compromise in
legibility.
--
Milos Prudek
---(end of broadcast)---
TIP 5:
Actually, if you declared idmember as SERIAL PRIMARY KEY, you could
just do:
I can't do that. idmember is a SERIAL PRIMARY KEY for members. Each
member can have many messages (msg table) with the same idmember column
value. See my original post.
--
Milos Prudek
---(end
Hi,
will I need nested transactions which - as I read - aren't
implemented, yet ?
I have some objects that rely on each other.
Each has a status like proposal, working, canceled.
table-A --- table-B --- table-C --- table-D
Those are (1, OO) relationships,
A status change above gets
Andreas wrote:
Hi,
will I need nested transactions which - as I read - aren't
implemented, yet ?
I have some objects that rely on each other.
Each has a status like proposal, working, canceled.
table-A --- table-B --- table-C --- table-D
Those are (1, OO) relationships,
A status
If you want the model where if any updates fail, all should be rolled
back, then you don't need nested transactions, just multiple aborts:
begin;
update d; if error abort;
update c; if error abort;
...
commit;
On Mon, 17 May 2004, Andreas wrote:
Hi,
will I need
17 matches
Mail list logo
