' || cast
(date_part('year', timestamp 'now') AS text );
- (10000 * this query):
standard select:54 sec
via prepare/execute: 4 sec (93% better)
IMHO it is nod bad.
- For standard query like
ckend help will help to all
and I'm sure that speed will grow up with persistent backend and
persistent caches without shared memory usage. There I can agree with
Tom :-)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQ
ELECT * FROM pg_class WHERE relname ~~ $1;
> ERROR: Parameter '$1' is out of range
My original syntax was:
PREPARE sel AS SELECT * FROM pg_class WHERE relname ~~ $1 USING text;
... USING is behind query.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu
On Sun, Apr 14, 2002 at 10:13:17PM +0200, Karel Zak wrote:
> > (2) Sometimes executing a PREPARE gives this warning:
> >
> > nconway=> prepare q1 as select * from pg_class;
> > WARNING: AllocSetFree: detected write past chunk end in TransactionCommandCont
t in EXECUTE under some circumstances (reported
> by Barry Lind)
> - fix some memory leaks (thanks to Karel Zak)
> - write more regression tests (make check still won't pass)
> - re-diff against CVS HEAD
> - more code cleanup, minor tweaks
>
> However, I've tentatively
pying from "A" to "B".
It require persistent backends of course.
Karel
PS. it's idea only and nothing other, the original qcache was idea
only too :-)
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://do
()? I think it's
nothing nice for local-memory cache too.
There is needful destory cached planns by one call of
MemoryContextDelete(). I hope that Neil wants still use
original "context-per-plan" cache.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.j
l API, like
list = ExtractQueryPlanOids( plan );
reg = RegisterOidsCallback( list, mycallback, mycallbackdata );
and now I can do:
mycallback(reg, mycallbackdata)
{
remove_plan_from_my_cache( (MyKey *) mycallbackdata );
UnregisterOidsCallback(reg);
}
K
On Tue, Apr 30, 2002 at 09:43:29AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > I have a question, how I will know how changes are relevant for my
> > query plan? IMHO is needful some hight-level API, like
>
> > list = ExtractQuer
On Tue, Apr 30, 2002 at 10:39:38AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > There must be possible define some callback specific data too, the
> > callback maybe will search query in some own specific cache and it
> > require some key.
l PREPARE/EXECUTE patch (it works in 7.1):
PREPARE name AS select * from tab where data=$1 USING text;
EXECUTE name USING 'nice text data';
IMHO is possible think about
EXECUTE name USING 'nice text'::text;
or other cast methods.
Karel
t's better than
use dagerous float and hard coded currency symbol.
For example in my country (and a lot of others) is the current money
datetype total useless. We have currency symbol after number, etc.
Sorry but _IMHO_ is better a less good supported types than more
bad datetypes.
how is current status of on-line backup log
based on WAL? The enterprise usage require it maybe more than
replication.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
ever will see end of the cycle :-)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 3: if posting/reading through
-
PostgreSQL 7.2 on i686-pc-linux-gnu, compiled by GCC 2.95.4
(1 row)
And it's in the docs too
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
--
andard ?
>
> Ditto for 15h -> 03 .
HH vs. HH24
test=# select to_char('33s 15h 10m 5months'::interval, 'HH24:MI:SS Month');
to_char
15:10:33 May
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~z
umber in range 1..12.
The to_char() convert date/time data to string and not to better formatted
interval. The right name for your request is to_interval().
TODO?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://
-
> .05.00 15:10:33
> (1 row)
I think, we can keep this behaviour for to_char(), the good thing
is that you can formatting interval to strings that seems like
standard time (15:10:33), etc.
The to_interval() will have another (you wanted) behaviour.
Karel
--
Karel Zak
On Tue, Jun 11, 2002 at 11:16:13AM +0200, Hannu Krosing wrote:
> On Tue, 2002-06-11 at 09:34, Karel Zak wrote:
> > I think, we can keep this behaviour for to_char(), the good thing
> > is that you can formatting interval to strings that seems like
> > standard time (15:
to_char
> -
> -00-10 00:00:00
I already said it. The to_char() is 'tm' struct interpreter and use
standard internal PG routines for interval to 'tm' conversion. We can
talk about why 100days is converted to '10' days and months aren'
ek' 'HH'---> '00'
7) '2week' 'HH'---> '336'
8) '2week' 'DD HH' ---> '14 00'
9) ???
I unsure what is best, Please, mark right outputs or write examples.
-- for all is probably right idea use '#
bly to_char() with special 'interval' behaviour or
format marks. But I still don't know how behaviour is right.
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of
tional".
OO in PostgreSQL means that you can create own operators, datetypes, functions...
Something about really Object Oriented you can found at:
http://www.odbmsfacts.com/
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL,
erface is:
encode( TEXT data, NAME from, NAME to );
where from/to are encoding names. The other way is use some struct
that handle this information -- like ARGS in trigger functions.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PH
ure with only one argument for encoding function. What if I want
> > to use one generic function for all encodings (for example as API to
> > iconv)?
>
> Use a simple wrap function.
How knows this function to/from encoding?
Karel
--
Karel Zak <
o_UTF-8(opaque, opaque, integer)
> RETURNS integer;
> CREAE CONVERSION myconversion FOR 'LATIN1' TO 'UNICODE' FROM
> function_for_LATIN1_to_UTF-8;
Hmm, but it require define "function_for_..." for each conversion.
For example trigger function I needn&#x
tring (null terminated C string)
> OPAQUE, -- destination string (null terminated C string)
> INTERGER-- source string length
> ) returns INTEGER; -- dummy. returns nothing, actually.
Karel
--
Karel Zak <[EMAIL PROTECT
and you (user) can't add new encoding without
pg_enc2name_tbl[] change. I original thought we can add new encodings
on-the-fly in 7.3 :-) You're right.
IMHO implement "User defined charsets(encodings)" will problem for
current libpq design.
Karel
--
Karel Zak
ined charsets(encodings)" will problem for
> > current libpq design.
>
> No, it's not a libpq problem, but more common "client/server" problem
> IMO. It's very hard to share dynamically created object (info)
> effectively between client and server.
blem. Strange question: is PQmblen() really
needful? I see it's used for result printing, but why backend not
mark size of field (word) to result? If backend good knows size of
data why not send this information to client togeter with data?
Karel
--
Karel Zak <[EMAIL PROTECTED
---
> 12996
> (1 row)
Is there some common convention of names? Why not pg_backend_pid()?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
On Thu, Aug 01, 2002 at 10:44:23AM -0400, Neil Conway wrote:
> On Thu, Aug 01, 2002 at 12:01:52PM +0200, Karel Zak wrote:
> > Is there some common convention of names?
>
> No, there isn't (for example, pg_stat_backend_id() versus
I know -- for this I asked. IMHO fo
ecated functions
In docs marked as "deprecated" and will removed in some major
release (for example in 8.0).
6/ ???
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
--
For example convert(), all datetype function like int(). The name
> > convenition must be like names in group 1/
>
> FYI, I have been proposing SQL99 compatible convert(). I would like to
> add it if no one objects.
I use convert() as example only. I think there is more function
On Thu, Aug 08, 2002 at 11:19:04PM +0200, Peter Eisentraut wrote:
> It seems we need a smart plan for handling the decimal point vs. comma
> issue. Observe: (lc_numeric = de_DE)
^^
It seems like hellish toy... :-)
Karel
--
Karel Zak &
allows to run backend as persistent (means not
startup/stop for each client connection).
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
ut more common is integrate query plan cache to SPI (saveplan).
I don't how it's in the current implementation.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---
o() calls. IMHO it can be compile
only if MEMORY_CONTEXT_CHECKING is define.
But I think there is not to much places which switching between
contexts and all are good commented (I hope, I wish :-)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQ
Thanks
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Mon, Sep 09, 2002 at 11:51:08AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > 1/ ExecuteQuery() (line 110). Why is needful use copyObject()? The
> > PostgreSQL executor modify query planns?
>
> Yes, and yes. Unfortunately.
Hmm, it'
In the server log file is:
TRAP: FailedAssertion("!(len > 0)", File: "utf8_and_iso8859_1.c", Line: 45)
If I use INSERT instead COPY it's OK.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.c
SQL and to_ascii() in
main tree. Comment?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
t; ! +
> > ! | 456.
> > ! | 4567890123456789.
> > ! | 123.
> > ! | 4567890123456789.
> > ! | -4567890123456789.
The results like this are right.
Karel
--
On Fri, Sep 20, 2002 at 09:24:00PM +0200, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > test=# select to_char(0,'FM9.9');
> > to_char
> > -
> > 0.
> > (1 row)
> >
> > test=# select to_char(1,'FM9.9');
> >
ate('402002', 'IWYYYY');
to_date
2002-09-30
(1 row)
test=# select to_date('012002', 'WW');
to_date
2002-01-01
(1 row)
test=# select to_date('012002', 'IW');
to_date
2001-12-31
(1 row)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
test=# select to_char('30-SEP-02'::date, 'WW IW Day D');
to_char
---
39 40 Monday2
SVRMGR> select to_char(to_date('29-SEP-02'), 'WW IW Day D') from dual;
TO_CHAR(TO_DATE('
i1 on ii a (cost=0.00..52.00 rows=1000 width=24)
-> Index Scan using i2 on ii b (cost=0.00..52.00 rows=1000 width=24)
Thanks,
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
-
On Wed, Oct 16, 2002 at 09:25:37AM -0400, Rod Taylor wrote:
> On Wed, 2002-10-16 at 09:19, Karel Zak wrote:
> >
> > Hi,
> >
> > I have SQL query:
> >
> > SELECT * FROM ii WHERE i1='a' AND i2='b';
> >
> > There're
(BTW backend is
multithread:-). IMHO use memory-context design for FE is good idea
if FE a lot works with memory. I already long time think about shared
lib with PostgreSQL mmgr...
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http
but worse.
Right.
There's solution: persisten backend (for example like classic
apache). This solve problem with lifetime of all persistent caches.
It's already in TODO.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, Postgre
;t want
to maintain my databases by SET command.
> profname
> session_per_user
> cpu_per_session
> cpu_per_call
> connect_time
> idle_time
> logical_reads_per_session
> logical_reads_per_call
... and a lot of others things in future.
Karel
--
Karel Zak <[EMAIL
,
age int
);
Comments? I nothinig found about OO in the current TODO. BTW, my
examples are only small part of possible OO features, the others
ideas are for example define PRIVATE/PUBLIC attributes in composite
types and methods, "SELECT p.name FROM person p WHERE p.pay->tax
;"
>
> The methods will probably have problems with syntax clashes with
> existing stuff.
Hmm, p.pay.tax() ?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
--
s is PostgreSQL useless in real DB aplication
(9) Think about full dynamic charset encoding (add new encoding on
the fly)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
ns ...;
SELECT * FROM myschema.tabname;
This solution allows use dblink as really transparent.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
---(end of broadcast)---
TIP 3: if posting/reading through
s. It's very interesting that nobody other wants it...
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Mon, Dec 02, 2002 at 08:56:41AM -0800, Joe Conway wrote:
> Karel Zak wrote:
> >On Sat, Nov 30, 2002 at 01:11:20PM -0800, Joe Conway wrote:
> >
> >>As I said, this is all very preliminary; comments, suggestions, requests
> >>are all welcome.
> >
> &
On Mon, Dec 02, 2002 at 12:48:38PM -0800, Christopher Kings-Lynne wrote:
> But if there is, then the sum/count(*) is nonsensical anyway.
You must to use it in SERIALIZABLE transaction isolation.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.
mm.');
to_date
2001-01-04
(1 row)
And primarily Oracle's to_date() is designed for operation that in
PG is solved via timestamp/date cast. For example you can use in
Oracle to_date('4.1.2001') without format mask and it's same thing
as 4.1.2001::date cast(&#
t must be disable, right must be something like:
set session authorization 'userA';
unset session authorization; <-- switch back to superuser
set session authorization 'userB';
..like as on Linux:
# su - zakkr
$ id -u
1000
$ su - jmarek
Password:
su: Authentication
rndard routines like copy query plan ... and Tom isn't sure with
query cache in shared memory...etc. Too much queries, but less answers :-)
Karel
>
> PS: Sorry for my english :(
Do you anytime read any my mail :-)
Karel
On Mon, May 07, 2001 at 02:48:11PM -0400, Bruce Momjian wrote:
>
> Can someone remind me what we are going to do with this?
>
> > This patch add to 7.0.2 code NOCREATETABLE and NOLOCKTABLE feature:
It's my old patch, it's usable and some people use it for 7.0.x. But
it's really temporary sol
m interested in using any other interface.
What dissect this work to two parts? First implement error codes and later
translation. IMHO transaction hasn't big importance (and will encapsulate
in elog() stuff) and is possible speculate about it later. Do you plannig
gettext stuff as a ./configur
KEY
> * ALTER TABLE ADD UNIQUE
And what
ALTER TABLE DROP PRIMARY KEY
ALTER TABLE DROP UNIQUE
BTW, it's a little cosmetic feature if we have CREATE/DROP INDEX :-)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~z
m.
> >
> > Patch applied.
>
> Wonderful! Thank you all! Do you have any kind of ETA for when this
> feature will be publicly available? Is this going to be included in 7.1.3
> or is it 7.2 stuff (just curious)?
I mean we're in 7.2 cycle -- into 7.1.x go bugfixes only.
#x27;d like, but I unsure with my time -- may be later (3 weeks?).
> Will be the new permission system in 7.2?
Probably not :-(
PS. ...may be someone in hackers list port it to 7.1 (see CC)
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PH
. This solution isn't acceptable for standard and official sources.
Probably is better no send this patch to [EMAIL PROTECTED],
somebody could be foggy from it.
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, h
e?
> c) executor should support execution of such Query node, properly
> extracting things out of function's return value and placing them into
> result attributes.
d) changes in fmgr
e) SPI support for table building/filling inside foo()
IMHO very cool and nice feature, but
E FUNCTION statement, like:
CREATE FUNCTION foo RETURNS( name1 int, name2 text) ;
If the foo is in the pg_class you can do "GRANT ... ON foo";
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http
On Wed, Jun 27, 2001 at 06:54:27AM -0400, Alex Pilosov wrote:
> On Wed, 27 Jun 2001, Karel Zak wrote:
>
> > On Wed, Jun 27, 2001 at 10:56:43AM +0200, Reinoud van Leeuwen wrote:
> > > >
> > > >> For the result from foo() you must somewhere define attrib
On Wed, Jun 27, 2001 at 08:42:07AM -0400, Alex Pilosov wrote:
> On Wed, 27 Jun 2001, Karel Zak wrote:
> This is a little bit better, but, results in following syntax:
> GRANT SELECT ON FOO(int4). I'm not sure if this really makes sense. Its
> not a select permission, its an exec
rning
records needs information about wanted result (number of columns, etc).
For example trigger functions has specific information by
"CurrentTriggerData" struct. For functions returning records we can
create special struct too. What?
Karel
--
Kar
f XML parser for large file? A dump from
SQL DB can be realy large. IMHO is for this (data dump from SQL DB) is
better SAX type of XML parser.
> an XSL stylesheet to transform an XML based database dump from some third
Yes, it's right way how use XML.
Karel
--
/postgresql/share/locale/de/LC_MESSAGES/#
^^^
use directly prefix from ./configure and ignore the prefix option
for 'make'. All other PG stuff are correct for this.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C,
On Mon, Aug 06, 2001 at 06:00:40PM +0200, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > $ make install prefix=/home/PG_DEVEL/X/
>
> > cp: cannot create regular file
> > /usr/lib/postgresql/share/locale/de/LC_MESSAGES/#
>
> I have fixed this. Note, however,
ent version of PG I must maintain
separate table for transformation "standard" names to PG encoding
names and vice-versa:-)
Well, I try send some patch.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~
like robust code :-)
Comments, better ideas?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 6: Have you sea
On Wed, Aug 15, 2001 at 05:16:42PM +0200, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > before some time I was discuss with Tatsuo and Thomas about support
> > for synonyms of encoding names (for example allows to use
> > "ISO-8859-1" as the encodi
.
> --
Good idea.
I have a question, the PostgreSQL encoding name "KOI8" is KOI8-R or
KOI8-U or both? I need it for correct alias setting.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, htt
mb/ is mix of standard files and files
with main()....
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
It's trouble create arrays with encoding stuff, like:
pg_encoding_conv_tbl[ ALT ]->to_mic
pg_encoding_conv_tbl[ SJIS ]->to_mic
Has this hole between 19..31 some effect?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreS
-> IBM866
> KOI8 -> KOI8_R
> UNICODE -> UTF_8 (Peter's suggestion)
>
Right.
But we will still need aliases UNICODE, ALT, KOI8 for back compatibility.
Thanks, I try fix all.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
htt
efined? In odbc/multibyte.h is again defined
all encoding identificators.
IMHO we can use for ODBC same solution as for libpq and compile it
with encname.c file too.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http:
> Bug?
>
> Oh, that must be a bug. Do yo want to take care of it by yourself?
I check and fix it. The 'createdb' script needn't check somethig, all
must be in backend.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~za
On Tue, Aug 21, 2001 at 10:00:21AM +0900, Hiroshi Inoue wrote:
> Karel Zak wrote:
> >
> > I found some other things:
> >
> > - ODBC -- here is some multibyte stuff too. Why ODBC code don't use
> > pg_wchar.h where is all defined? In odbc/multibyte
s clean internal code for encoding names to faster
and non-duplicated code (use same code for FE and BE).
Well, I prepare it with total back compatible output for all current
routines (pg_char_to_encoding too) and new names will visible by new
routines only (suggested database_chara
sal
about it too).
Karel
PS. L. Ellison has still better GRANT/REVOKE stuff than PG:-(
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)
ata directly in batea by binary cursor.
Comments?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
4 -4
Change the conditionals so the mips + gcc code here doesn't apply for Irix.
The code in s_lock.h should get used.
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of
l 'OR' problem :-)
Karel
On Wed, Aug 29, 2001 at 01:03:25PM +0200, Karel Zak wrote:
>
> Hi,
>
> from current CVS:
>
> ./configure --prefix=/usr/lib/postgresql \
> --enable-multibyte \
> --enable-
> > Does anyone else have work that they're trying to finish up before
> > we go beta?
I'm fixing and add some features to "to_char" (new to_char(interval) ).
Maybe I will finish it on this Friday.
Karel
--
Karel Zak <[EMAIL PROTECTED]&
d more expensive for transfer between FE
and BE?
A base64 problem is that encode all chars in string, but in the
real usage some data contains "bad" chars occasional only.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
my previous (31 Aug) patch with to_char()
stuff? I want fix this bug in really actual CVS code. Thanks.
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)-
arbage pointer
> > > if there was no such last query.
> >
> > You are right it's bug. For the 'RM' in non-fillmode is to_char() quiet.
> > I will fix it for 7.2.
>
> Karel, I assume you will send in a patch yourself, right?
Right. It nee
be
libpq don't set client encoding if it's default SQL_ASCII, but
I'm almost sure that I check this case).
A simple and robus solution is in the begin of mbutils.c set default
ClientEncoding to SQL_ASCII (like default DatabaseEncoding). Bruce, can
you change it? It's one lin
In odbc/multibyte.h is again defined
> > all encoding identificators.
Probably done, it check ODBC maintainer.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
-
> On Sat, Sep 08, 2001 at 10:29:38AM +0200, Karel Zak wrote:
> > On Fri, Sep 07, 2001 at 09:06:18PM -0500, Larry Rosenman wrote:
> > > I finally got all the way through a compile set:
> > >
> > > CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-sys
On Fri, Sep 07, 2001 at 10:39:19AM -0400, Bruce Momjian wrote:
> > Karel Zak <[EMAIL PROTECTED]> writes:
> > >> But here is the tail of the output:
> > >> UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled
> > >> UX:acom
vs add src/utils/mb/encname.c
* removed file:
cvs remove src/utils/mb/common.c
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---(end of broadcast)-
ere can't be used static default encoding as for DatabaseEncoding, because
typical code is
if (!ClientEncoding)
/* ...means "if user doesn't set itself client
* encoding by SET command"
*/
ClientEncoding = DatabaseEncoding;
and if you
1 - 100 of 262 matches
Mail list logo
