pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: JanWieck@t-online.de
To: Kyle <kyle@actarg.com>
Cc: JanWieck@t-online.de
Cc: JanWieck@Yahoo.com
Cc: pgsql-sql@postgresql.org
Subject: Re: TCL updates
Date: Tue, 25 Jul 2000 00:47:18 +0200 (MEST)
Message-ID: <200007242247.AAA17144@hot.jw.home> (raw)
In-Reply-To: <397C7616.B616EC10@actarg.com>

Kyle wrote:
> Jan wrote:
> >   Beginning  with Tcl 8.0, dual ported objects got used to deal
> >    with values. These have (amongst performance issues) alot  of
> >    benefits.  Changing  all  the  call  interfaces would make it
> >    impossible to use PL/Tcl with a  pre  8.0  Tcl  installation.
> >    Since  we're  now  at Tcl 8.3 (the last I've seen), ISTM it's
> >    not a bad decision to force the upgrade.
> >
> >    Comments?
>
> Jan, I would support this upgrade.  I think TCL runs much faster with
> the dual ported calls, right?

    After  writing  the  above  (and looking at the code again) I
    realized that most of the  Tcl  calls  into  the  PL  handler
    provided  C  functions go through strings anyway. Each single
    attribute value must do so, because in the worst case someone
    might  have replaced the output function for int4, and PL/Tcl
    has to be consistent with that.

    So I left that one as is for now.

> I would also like to see proper support for nulls in TCL functions as
> this has caused us some problems in the past.

    In CURRENT  sources,  there  are  two  new  PL/Tcl  commands.
    "argisnull  n"  determines  if  one specific call argument is
    NULL. "return_null" will do exactly that.

> BTW, any news on this:  Is there a plan for a way to allow a FK
> reference to a table without giving the user select,update privilege on
> the referenced table?  This is currently causing us some grief in our
> design.

    I'm writing on a proposal to replace  the  entire  permission
    system  to  a more normalized and generalized approach.  Stay
    tuned.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #





view thread (2+ messages)

Message-ID: <200007242247.AAA17144@hot.jw.home>
Permalink:  ../200007242247.AAA17144@hot.jw.home/
Also on:    postgresql.org/message-id/200007242247.AAA17144@hot.jw.home

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: JanWieck@t-online.de, kyle@actarg.com, JanWieck@Yahoo.com
  Subject: Re: TCL updates
  In-Reply-To: <200007242247.AAA17144@hot.jw.home>
  References: <397C7616.B616EC10@actarg.com> <200007242247.AAA17144@hot.jw.home>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox