FET stands for Further-eastern European Time and is the official time in
e.g. Belarus (Europe/Minsk).
The attched patch adds FET to the list of Default timezone abbreviations.
- Marc Balmer
diff --git a/src/timezone/tznames/Default b/src/timezone/tznames/Default
index 1369f47..7223ce5 100644
The attached patch would add the FET timezone abbreviation to the
Default list _and_ the list of european abbreviations.
- mb
diff --git a/src/timezone/tznames/Default b/src/timezone/tznames/Default
index 1369f47..7223ce5 100644
--- a/src/timezone/tznames/Default
+++
---
On Sat, Oct 6, 2012 at 11:18:43AM +0200, Marc Balmer wrote:
The attached patch would add the FET timezone abbreviation to the
Default list _and_ the list of european abbreviations.
- mb
diff --git a/src/timezone/tznames/Default b/src/timezone/tznames/Default
index 1369f47..7223ce5 100644
Am 08.10.12 11:07, schrieb Simon Riggs:
On 8 October 2012 09:05, Heikki Linnakangas hlinnakan...@vmware.com wrote:
* Make the tz file configurable, so people can be more explicit about
what *they* mean by certain codes, to avoid the need for choosing
between countries. For example, someone
Am 08.10.12 16:53, schrieb Bruce Momjian:
On Mon, Oct 8, 2012 at 12:14:15PM +0200, Marc Balmer wrote:
A good starting point would be to take the timezone information directly
from the the files IANA distributes, instead of manually copying and
maintaining them in a separate file. If no one
this part). It
has been carefully designed to handle memory the right way. We use this
since a long time.
What do you think?
/*
* Copyright (c) 2008, 2009, 2010 Marc Balmer m...@msys.ch
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification
Am 05.12.2010 um 11:57 schrieb Heikki Linnakangas
heikki.linnakan...@enterprisedb.com:
On 05.12.2010 12:10, Magnus Hagander wrote:
On Sun, Dec 5, 2010 at 10:22, Marc Balmerm...@msys.ch wrote:
I am suggesting adding a function to libpq:
PGresult *PQvexec(PGconn *conn, const char *fmt,
Am 06.12.10 15:37, schrieb Merlin Moncure:
On Sun, Dec 5, 2010 at 5:10 AM, Magnus Hagander mag...@hagander.net wrote:
On Sun, Dec 5, 2010 at 10:22, Marc Balmer m...@msys.ch wrote:
I am suggesting adding a function to libpq:
PGresult *PQvexec(PGconn *conn, const char *fmt, ...);
It behaves
Currently there are FETCH and the (non standard) MOVE commands to work
on cursors.
(I use cursors to display large datasets in a page-wise way, where the
user can move per-page, or, when displaying a single record, per record.
When the user goes back from per-record view to page-view, I have to
2015-02-09 10:37 GMT+01:00 Marc Balmer m...@msys.ch mailto:m...@msys.ch:
Currently there are FETCH and the (non standard) MOVE commands to work
on cursors.
(I use cursors to display large datasets in a page-wise way, where the
user can move per-page, or, when displaying
Am 09.02.15 um 11:47 schrieb Marc Balmer:
Am 09.02.15 um 10:46 schrieb Heikki Linnakangas:
[...]
You could fairly easily write an extension to do that, btw. A C function
could call GetPortalByName() and peek into the PortalData.portalPos field.
Would
PGresult *PQdescribePortal
Am 09.02.15 um 10:46 schrieb Heikki Linnakangas:
[...]
You could fairly easily write an extension to do that, btw. A C function
could call GetPortalByName() and peek into the PortalData.portalPos field.
Would
PGresult *PQdescribePortal(PGconn *conn, const char *portalName);
from libpq
Am 09.02.15 um 13:13 schrieb Hakan Kocaman:
Hi,
2015-02-09 10:37 GMT+01:00 Marc Balmer m...@msys.ch mailto:m...@msys.ch:
(I use cursors to display large datasets in a page-wise way, where the
user can move per-page, or, when displaying a single record, per record.
When
I am looking for ways to ensure referential integrity on large objects.
Something like having a column myoid in a table that holds an oid of a large
object, and which throws an error when the referenced large object should be
unlinked. Like "myoid references pg_largeobject(loid)", which does
14 matches
Mail list logo
