"David J. R. Brook" <[EMAIL PROTECTED]> writes:
> I'm trying to use the 'bit' and 'varbit' datatypes in a table.
What version are you running? IIRC, there are types calling themselves
bit and varbit in 7.0, but they're only stubs; the first real support
for bitstrings is in 7.1.
On Thu, Jan 25, 2001 at 02:29:55PM -0500, Brett W. McCoy wrote:
> On Thu, 25 Jan 2001, wrote:
>
> > I am not able to get Wildcards in PostgreSQL, I know its * (asterisk), but
> > its not working. can someone show me a example or something?
>
> Wildcards where? You can use * to mean all the fie
On Fri, 26 Jan 2001, Mark A. Summers wrote:
> I am having trouble with the following query taking forever:
> -
> SELECT * FROM ret108108_00, product
> WHERE ret108108_00."isbn" = product."Item1"
>
> AND product."SuperCategory" = '1'
> AND product."PublisherCode" = 'ZON'
> ORDER BY ret10
these are common errors on the mysql side also. Most likely poor planing on the
Access end.
Emils Klotins wrote:
> > > I want to use pg 7.x as a backend for a MS Access application. I linked a
> > > table via ODBC, using the newest ODBC driver. I can open and view tables. But
> > > after I inse
On Thu, 25 Jan 2001, wrote:
> I am not able to get Wildcards in PostgreSQL, I know its * (asterisk), but
> its not working. can someone show me a example or something?
Wildcards where? You can use * to mean all the fields in a table in a
SELECT statement, but if you are using LIKE in a WHERE c
I got a response in email, so I assume the author wants to remain anonymous.
He wrote:
>There's an option to psql (I think -E or -e) that will make it echo all
>the SQL queries it does when you do something like "\d table"
So running a "psql -E " and then doing a "\d " will give you
information
I am having trouble with the following query taking forever:
-
SELECT * FROM ret108108_00, product
WHERE ret108108_00."isbn" = product."Item1"
AND product."SuperCategory" = '1'
AND product."PublisherCode" = 'ZON'
ORDER BY ret108108_00.qty DESC LIMIT 100
The problem is the second AND
Hi all,
I am trying to invoke a postgres sql function though JDBC using the
CallableStatment object. I have build the driver with it's jdbc1.2 option.
However, I am getting the following exception "Callable statments are not
supported at this time"
Does any one have an idea if there is a work ar
> PLEASE ADVISE HOW I SHOULD ALTER THE COMMAND:
>
> <$NOW;DD;>
>
> TO GIVE ME A DATE THAT IS X DAYS FORWARD
>
> ie: I WISH TO REPRESENT A DATE IN FORM WHICH IS A 7 DAYS FORWARD
> OF THE DATE NOW.
( now() + '7 days'::interval )::date (or ::datetime, whichever you
need)
Emils
> > I want to use pg 7.x as a backend for a MS Access application. I linked a
> > table via ODBC, using the newest ODBC driver. I can open and view tables. But
> > after I insert a new record, all fields will contain "#deleted". When I
> > reopen the table, the inserted data is displayed correctly
I'm trying to use the 'bit' and 'varbit' datatypes in a
table. The demo file 'varbit.demo.sql' runs fine but
when I
try to INSERT data into the table I get a message:
ERROR: zpbit_in: bit string of size 8 cannot be
written into
bits(1)
I can add data to the table th
Hi all,
having this simple table:
create table foo (attribute text);
and this simple function:
create function f()
returns foo
as
'
select ' 'test' '::text
'
langauge 'sql' ;
When I execute (though psql) select f();
I get the following result
f
136411800
instead of
Hi everybody
I have quite a query to build and don't know, whether this can be done with
SQL.
Please see the attachment for the details.
Any help is really appreciated !!
Thanks in advance jr
(See attached file: queryDetails.doc)
PFISTER + PA
I am not able to get Wildcards in PostgreSQL, I know its * (asterisk), but
its not working. can someone show me a example or something?
Christopher Sawtell <[EMAIL PROTECTED]> writes:
> I built from sources of v-7.0.0 are there some patches somewhere, or do I
> have to d/l the whole thing via cvs?
There's no patch (if there were, it'd be enormous). Either pull from
CVS or use a beta or nightly-snapshot tarball (see pub/dev on o
On Sat, 27 Jan 2001 06:44, Glen and Rosanne Eustace wrote:
> > Could one of you try it in 7.1 (beta3 or later)?
ok, I'll have a go at upgrading. I'll try to get it done either this evening
or tomorrow. Hopefully ready on Monday.
I built from sources of v-7.0.0 are there some patches somewhere,
> Yep, you need to do whole shebang of dumping and reloading.
Hmmm.
I think I'll just cheat for a while and add 364 days, hopefully before
the end of NZ daylight savings, the production release of 7.1 will be
out. I really don't want to upgrade twice.
Glen.
Tom,
> Say what?
>
> regression=# create function foo(int) returns int as '
> regression'# begin
> regression'# if $1 > 10 then return $1;
> regression'# end if;
> regression'# return $1 - 1;
> regression'# end;' language 'plpgsql';
> CREATE
Hmmm? When I've tried creating similar functio
Josh Berkus <[EMAIL PROTECTED]> writes:
> Currently (7.0.3) the PLPGSQL function compiler permits only one RETURN
> statment, at the end of the function. RETURN statements placed
> elsewhere cause a compile error.
Say what?
regression=# create function foo(int) returns int as '
regression
Kyle wrote:
> The only complication is
> that there are a class of records which the user should be able to view, but not
> modify. For example,
> the employee can create and modify working records as long as the only
> modification to their status
> is to move them on to "open status" (creating
Kyle wrote:
> The only complication is
> that there are a class of records which the user should be able to view, but not
> modify. For example,
> the employee can create and modify working records as long as the only
> modification to their status
> is to move them on to "open status" (creating
On Sat, 27 Jan 2001, Glen and Rosanne Eustace wrote:
> Is 7.0.3 to 7.1B? simply a reinstall or do I need to unload/reload the
> database.
Yep, you need to do whole shebang of dumping and reloading.
-- Brett
http://www.chapelperilous.net/~bmccoy/
> regression=# select '31/12/2000'::date + '365 days'::timespan;
> ?column?
>
> 2001-12-31 00:00:00+13
> (1 row)
>
> This looks promising but I wouldn't call it conclusive, particularly
> since you're probably using a different OS than I am (I'm on HPUX
> 10.20).
On Sat, 27 Jan 2001, Glen and Rosanne Eustace wrote:
> If some one else is running 7.1 already and can just change their
> timezone to New Zealand DT and report the results it would be great.
Here ya are:
cp=> set time zone 'NZ';
SET VARIABLE
cp=> select '12/31/2000'::date + '1 year'::interval
"Glen and Rosanne Eustace" <[EMAIL PROTECTED]> writes:
> If some one else is running 7.1 already and can just change their
> timezone to New Zealand DT and report the results it would be great.
Well, with TZ set to NZST-12NZDT I get
regression=# select '31/12/2000'::date::timestamp;
?col
> Could one of you try it in 7.1 (beta3 or later)? We've changed some
> details of the way daylight-savings transitions are handled in
> date-to-timestamp conversions, so I think this might be fixed now.
> It's worth checking anyway.
I would prefer not to upgrade right at the moment, as my devel
Jan, Tom, etc:
Currently (7.0.3) the PLPGSQL function compiler permits only one RETURN
statment, at the end of the function. RETURN statements placed
elsewhere cause a compile error.
This, combined with the lack of an ELSEIF statement, has forced me into
sometimes 7 levels of ne
Jan Wieck wrote:
> Tom Lane wrote:
>
> > This might be better done with a trigger than a rule. For one thing,
> > a trigger can easily raise an exception. MHO is that rules are good
> > when you need to update multiple rows in other tables when certain
> > things happen. If you just want to va
Tom Lane wrote:
Kyle <[EMAIL PROTECTED]> writes:
> If someone happens to know the primary key of a record they should
not be
> able to access, and they try to update it, I would like the backend
to
> ignore the query (or better yet, raise an exception but I haven't
figured
> out how to do that).
Tom Lane wrote:
> Kyle <[EMAIL PROTECTED]> writes:
> > If someone happens to know the primary key of a record they should not be
> > able to access, and they try to update it, I would like the backend to
> > ignore the query (or better yet, raise an exception but I haven't figured
> > out how to
Mr. Reid,
> To answer your question, it is a bit hard to say at the moment as the
> design schema for our project has only just been started. The draft
> versions of the ISO standard that I have seen use an object oriented
> data model, so to me it makes sense to try and keep the database sc
Saluton!
On Thu, Jan 25, 2001 at 11:12:34AM +0100, Markus Wagner wrote:
...
> Some of the data are strings containing the apostrophe "'" which I use
> as string delimiter.
>
> How can I put these into my database using the INSERT statement?
I always use this sub:
#
# This sub adapted f
Tom Lane wrote:
> Kyle <[EMAIL PROTECTED]> writes:
> > If someone happens to know the primary key of a record they should not be
> > able to access, and they try to update it, I would like the backend to
> > ignore the query (or better yet, raise an exception but I haven't figured
> > out how to d
Christopher Sawtell <[EMAIL PROTECTED]> writes:
> On Fri, 26 Jan 2001 12:46, Glen and Rosanne Eustace wrote:
> [ ... ]
>> template1=# select '31/12/2000'::date + '365 days'::timespan;
>> ?column?
>>
>> 2002-01-01 00:00:00+13<<< Wrong
>> (1 row)
> [ ... ]
> I
On Fri, 26 Jan 2001 12:46, Glen and Rosanne Eustace wrote:
[ ... ]
> template1=# select '31/12/2000'::date + '365 days'::timespan;
> ?column?
>
> 2002-01-01 00:00:00+13<<< Wrong
> (1 row)
[ ... ]
I get the same result. This business of crooked date
35 matches
Mail list logo
