On Wed, Dec 21, 2005 at 11:52:56 -0800,
Mark <[EMAIL PROTECTED]> wrote:
> Hello everybody,
>
> I'm looking for an elegant SQL statement that will work in
> Postgresql, MySQL and ORACLE.
> The query will be executed by Java client.
>
> To have this query for Postgresql is priority number one.
>
Thank you again for the clarification!
> I'm not sure how to explain it any more clearly: the backslash in this
> example is not a backslash. It's a byte within a multibyte character,
> which *entirely coincidentally* happens to have the same numeric value
> as an ASCII backslash. But it isn't a
"CN" <[EMAIL PROTECTED]> writes:
> INSERT INTO y VALUES ('y\134na');
> --"y\" and "na" are two Big5 characters.
I'm not sure how to explain it any more clearly: the backslash in this
example is not a backslash. It's a byte within a multibyte character,
which *entirely coincidentally* happens to h
> No, I'm suggesting that it shouldn't be let loose on Big5 data when it
> evidently hasn't a clue about that encoding. The byte in question
> *is not* a backslash, it's not even an independent character; and so
> changing it on the assumption that it is logically a backslash simply
> breaks the d
"CN" <[EMAIL PROTECTED]> writes:
>> Seems to me that you need to fix your broken middleware --- it has no
>> business doing that.
> Are you suggesting that the middleware should not escape backslashes in
> the first place?
No, I'm suggesting that it shouldn't be let loose on Big5 data when it
evi
Many thanks for the lightening fast answer!
> > The database cluster is initialized to use UNICODE. The client encoding
> > is set to BIG5. The middleware escapes the backslash in the following
> > string before writing to TEXT/VARCHAR column in server:
>
> > a5 5c af e0
>
> Seems to me that you
"CN" <[EMAIL PROTECTED]> writes:
> The database cluster is initialized to use UNICODE. The client encoding
> is set to BIG5. The middleware escapes the backslash in the following
> string before writing to TEXT/VARCHAR column in server:
> a5 5c af e0
Seems to me that you need to fix your broken m
Hello!
The database cluster is initialized to use UNICODE. The client encoding
is set to BIG5. The middleware escapes the backslash in the following
string before writing to TEXT/VARCHAR column in server:
a5 5c af e0
This is a string comprises Big5 characters each of 2 octets big. Note
that the
Bruce Momjian writes:
>> On Fri, Dec 23, 2005 at 11:04:50AM -0500, Tom Lane wrote:
>>> It's not that easy --- in the MVCC world there simply isn't a unique
>>> count that is the right answer for every observer. But the idea of
>>> packaging a count(*) mechanism as an index type seems like it migh
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> On Fri, Dec 23, 2005 at 11:04:50AM -0500, Tom Lane wrote:
> > It's not that easy --- in the MVCC world there simply isn't a unique
> > count that is the right answer for every observer. But the idea of
> > packaging a count(*) mechani
Am Freitag, 23. Dezember 2005 22:06 schrieb robert mena:
> GRANT CREATE,REFERENCES ON DATABASE test TO testadm;
>
> \z
> Access privileges for database "test"
> Schema | Name | Type | Access privileges
> +--+--+---
>
> How can I specify that the user testadm can per
"robert mena" <[EMAIL PROTECTED]> wrote
>
> How can I specify that the user testadm can perform those actions to this
> database?
Use GRANT command (the opposite is REVOKE). I suppose you are using 8.1:
http://www.postgresql.org/docs/8.1/static/sql-grant.html
Regards,
Qingqing
-
Hi,
I am new to postgres but coming from a MySQL enviroment.
I am confused with the necessary steps to create users and restrict
them to access/delete/insert/update data and create/delete/alter tables
in a specific database.
I've created a database test and a user testadm
createdb test
create
On Fri, Dec 23, 2005 at 11:36:54AM -0500, Tom Lane wrote:
> Michael Adler <[EMAIL PROTECTED]> writes:
> > I'm investigating a problem that happened last night and I would
> > appreciate any recommendations. The logs indicate that the disks were
> > full, but I truly doubt that since we only use abo
Martijn van Oosterhout writes:
> AFAICS two big problems with using an index type:
> 1. The index isn't told when the tuple is deleted.
Hm, good point ... we could make it do so but for ordinary deletes it'd
be a waste of cycles to open indexes at all.
> 2. The server expects to be able to look
On Fri, Dec 23, 2005 at 11:04:50AM -0500, Tom Lane wrote:
> It's not that easy --- in the MVCC world there simply isn't a unique
> count that is the right answer for every observer. But the idea of
> packaging a count(*) mechanism as an index type seems like it might be
> a good one. I don't thin
Is it possible to isolate logging for each individual database?
For example, lets say I have 3 databases: db1, db2, db3. And I want to
log db activity (statements, login/logout, etc..) db1, db2, db3 like
$PGDATA/db1, $PGDATA/db2, $PGDATA/db3, respectively.
Currently everything is logged in $PGDAT
Michael Adler <[EMAIL PROTECTED]> writes:
> I'm investigating a problem that happened last night and I would
> appreciate any recommendations. The logs indicate that the disks were
> full, but I truly doubt that since we only use about 14GB out of the
> available 65GB.
> I found entries like this
I'm investigating a problem that happened last night and I would
appreciate any recommendations. The logs indicate that the disks were
full, but I truly doubt that since we only use about 14GB out of the
available 65GB.
I found entries like this in the logs:
ERROR: could not write block 2354 of
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> One way to conceptually tackle this count(*) issue would be to create a new
> index type for it. The index type would (logically) just need to implement
> insert and delete operations and keep a running count with a big lock around
> it. Users cou
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Unless I'm missing something that wouldn't use an index either,
> because the planner wouldn't know what value to compare start_date
> against without hitting each row to find that row's time_to_live.
> But something like this should be able to use an expr
One way to conceptually tackle this count(*) issue would be to create a new
index type for it. The index type would (logically) just need to implement
insert and delete operations and keep a running count with a big lock around
it. Users could then choose to trade off concurrent performance ag
On 12/23/05, Karsten Hilbert <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 22, 2005 at 05:05:49PM -0700, Trent Shipley wrote:
>
> > On Wednesday 2005-12-21 07:50, Karsten Hilbert wrote:
>
> > > I would assume quite a few people would use table
> > > inheritance in a simple way were it available in a mor
On Thu, Dec 22, 2005 at 05:05:49PM -0700, Trent Shipley wrote:
> On Wednesday 2005-12-21 07:50, Karsten Hilbert wrote:
> > I would assume quite a few people would use table
> > inheritance in a simple way were it available in a more
> > convenient fashion: to transport fields, primary and foreign
On Thu, 2005-12-22 at 12:42 -0500, Jaime Casanova wrote:
> On 12/22/05, Ted Byers <[EMAIL PROTECTED]> wrote:
> >
> > INSERT INTO foo (auto,text)
> > VALUES(NULL,'text'); # generate ID by inserting NULL
>
> and this of course is bad... if a insert NULL i want the NULL to be inserte
On 12/23/05, Carlos Moreno <[EMAIL PROTECTED]> wrote:
> Marko Kreen wrote:
>
> >On 12/22/05, Carlos Moreno <[EMAIL PROTECTED]> wrote:
> >
> >>The problem is, when I execute the SQL statement:
> >>
> >>create or replace function sha1 ;
> >>
> >>for the second time (i.e., after making modificat
26 matches
Mail list logo
