Hello all,
I have problem with Cisco - it do not accept (do not use) my
Framed-IP-Address attribute, but only use Cisco's internal
IP pools for allocating IPs for PPTP users. Is it possible
for Cisco to accept RADIUS's Framed-IP-Address attribute to
correct setting up IP ad
Bors Folgmann ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
subselect returns more than one tuple where not possible
Long Description
I'm using postgresql 7.2.2 on RedHat Linux 8.0.
Inside a transaction (PL/pgSQL function) I u
[EMAIL PROTECTED] writes:
> Sometimes when running concurrent updates, the function fails with ERROR: More than
>one tuple returned by a subselect used as an expression.
Can't say much about this when you aren't showing us the
concurrent-update sequence of operations.
re
> > Difficult to do, when those privileges might be recorded in
> > databases you're not even connected to at the time of the drop.
>
> I belive it would be pretty difficult, but leaving it "just like
> that" creates ssecurity breach (imagine someone droping user,
> beliving that everytinh is o.k.
Ruslan,
I'm afraid that you sent your message to the PostgreSQL Bugs Mailing
List, where we cannot help you with Cisco problems. Please try an
appropriate Cisco mailing list.
-Josh Berkus
---(end of broadcast)---
TIP 5: Have you checked our extens
[Tom Lane]
| This is not a bug, but an intentional change: float->numeric isn't
| an implicit cast anymore.
Ah. I didn't find it in the "Observe the following incompatibilities"
of the HISTORY file, so I imagined it could be unintentional.
Thanks for replying!
Sverre.
--
[EMAIL PROTECTE
I am having trouble with a function round that used to work in 7.2.1
PostgreSQL was updated to 7.3.1 from 7.2.1, the data was re-loaded into
7.3.1 with no complaints from the DB engine but, at application run
time, we do get the error:
Function round(double precision, integer) does not exists
Co
On Tue, 7 Jan 2003, Tom Lane wrote:
> Apparently, our configure script thinks you have getopt_long(), but you
> really don't. Can you look into the situation and figure out why
> configure is confused?
>
> It surprises me that this would happen when 7.2 worked okay --- I don't
> think we change
Tom Lane wrote:
>
> [EMAIL PROTECTED] writes:
> > Cursor scrolling broken in 7.3.1 (works in 7.2.1)
>
> That's a fairly sweeping claim.
>
> I have found a bug that explains this problem for the case where the
> cursor retrieves a single row using a unique index. Have you seen it
> happen in any
When inserting a row into a table, if there is a varchar
column and if in that column the value to be inserted is a zero length string
(like ‘’), then instead of writing a null value, PostgreSQL writes
that zero length string. We are able to do this with delphi
which generates such sql inse
10 matches
Mail list logo
