I've posted a bug report twice through the web based interface, most
recently last Friday. To date, my bug has never shown up in the archives
for the pg-bugs list.
Chris Fischer
Database Engineer
<http://www.channeladvisor.com/>
ChannelAdvisor Corporation
2701 Aerial Cen
Here's a PL/pgsql implementation I wrote.I'm sure critics will be
able to improve upon it:
CREATE or REPLACE FUNCTION "common"."newid"()
RETURNS "pg_catalog"."varchar" AS
$BODY$
DECLARE
v_seed_value varchar(32);
BEGIN
select
md5(
inet_client_addr()::varchar ||
timeofday() ||
inet_server_ad
You'll need to do something like this, called a correlated subquery:
Select t1.term_id, t1.term_name, t1.term_starts, t2.term_id as
next_term
From term t1, term t2
where t2.term_starts = (select min(t3.term_starts) from term t3 where
t3.term_starts > t1.term_starts)
-Original Message-
F
All of Oracle's (non-float) number types are variable size numbers with an
ordinal and a mantissa. This makes Oracle number very efficient for smaller
values as compared to fixed size integers, but less efficient with larger
values. NUMBER has a maximum precision of 38 digits with a scale of -
tement"
with the same function oid each time.
When I rerun the script, the oid in the error changes. So, I'm guessing
that it has to do with dropping/recreating my "dropprocsbyname"
function, but I cannot figure out when its being cached and how to
overcome the error.
Chris Fischer
Database Engineer
