1997-04-17 15:50:57 +02:00
|
|
|
/*
|
1997-04-23 08:09:36 +02:00
|
|
|
* Routines for handling of 'SET var TO', 'SHOW var' and 'RESET var'
|
|
|
|
* statements.
|
1997-04-17 15:50:57 +02:00
|
|
|
*
|
1997-08-12 22:16:25 +02:00
|
|
|
* $Id: variable.c,v 1.13 1997/08/12 20:15:50 momjian Exp $
|
1997-04-17 15:50:57 +02:00
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
#include <stdio.h>
|
1997-04-17 15:50:57 +02:00
|
|
|
#include <string.h>
|
1997-06-20 19:17:03 +02:00
|
|
|
#include <ctype.h>
|
1997-03-25 10:44:00 +01:00
|
|
|
#include "postgres.h"
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
#include "miscadmin.h"
|
1997-03-25 10:44:00 +01:00
|
|
|
#include "tcop/variable.h"
|
1997-04-24 17:41:37 +02:00
|
|
|
#include "utils/builtins.h"
|
|
|
|
#include "optimizer/internal.h"
|
|
|
|
|
|
|
|
extern Cost _cpu_page_wight_;
|
|
|
|
extern Cost _cpu_index_page_wight_;
|
1997-04-29 06:38:58 +02:00
|
|
|
extern bool _use_geqo_;
|
1997-06-02 13:00:57 +02:00
|
|
|
extern int32 _use_geqo_rels_;
|
1997-05-20 12:31:42 +02:00
|
|
|
extern bool _use_right_sided_plans_;
|
1997-03-25 10:44:00 +01:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
#if USE_EURODATES
|
|
|
|
#define DATE_EURO TRUE
|
|
|
|
#else
|
|
|
|
#define DATE_EURO FALSE
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
struct PGVariables PGVariables =
|
|
|
|
{
|
|
|
|
{ DATE_EURO, Date_Postgres }
|
|
|
|
};
|
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-06-02 13:00:57 +02:00
|
|
|
static const char *get_token(char **tok, char **val, const char *str)
|
|
|
|
{
|
|
|
|
const char *start;
|
|
|
|
int len = 0;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
|
|
|
*tok = NULL;
|
|
|
|
if (val != NULL) *val = NULL;
|
|
|
|
|
1997-06-02 13:00:57 +02:00
|
|
|
if ( !(*str) )
|
|
|
|
return NULL;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-06-02 13:00:57 +02:00
|
|
|
/* skip white spaces */
|
1997-06-20 19:17:03 +02:00
|
|
|
while (isspace(*str)) str++;
|
1997-06-02 13:00:57 +02:00
|
|
|
if ( *str == ',' || *str == '=' )
|
|
|
|
elog(WARN, "Syntax error near (%s): empty setting", str);
|
1997-06-20 19:17:03 +02:00
|
|
|
|
|
|
|
/* end of string? then return NULL */
|
1997-06-02 13:00:57 +02:00
|
|
|
if ( !(*str) )
|
|
|
|
return NULL;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
|
|
|
/* OK, at beginning of non-NULL string... */
|
1997-06-02 13:00:57 +02:00
|
|
|
start = str;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-06-02 13:00:57 +02:00
|
|
|
/*
|
|
|
|
* count chars in token until we hit white space or comma
|
|
|
|
* or '=' or end of string
|
|
|
|
*/
|
1997-06-20 19:17:03 +02:00
|
|
|
while ( *str && (! isspace(*str))
|
|
|
|
&& *str != ',' && *str != '=' )
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
|
|
|
str++;
|
|
|
|
len++;
|
|
|
|
}
|
|
|
|
|
1997-06-20 19:17:03 +02:00
|
|
|
*tok = (char*) PALLOC(len + 1);
|
1997-08-12 22:16:25 +02:00
|
|
|
strNcpy (*tok, start, len);
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
/* skip white spaces */
|
1997-06-20 19:17:03 +02:00
|
|
|
while ( isspace(*str)) str++;
|
|
|
|
|
|
|
|
/* end of string? */
|
|
|
|
if ( !(*str) ) {
|
|
|
|
return(str);
|
|
|
|
|
|
|
|
/* delimiter? */
|
|
|
|
} else if ( *str == ',' ) {
|
1997-06-02 13:00:57 +02:00
|
|
|
return (++str);
|
|
|
|
|
1997-06-20 19:17:03 +02:00
|
|
|
} else if ((val == NULL) || ( *str != '=' )) {
|
1997-06-02 13:00:57 +02:00
|
|
|
elog(WARN, "Syntax error near (%s)", str);
|
1997-06-20 19:17:03 +02:00
|
|
|
};
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
str++; /* '=': get value */
|
|
|
|
len = 0;
|
|
|
|
|
|
|
|
/* skip white spaces */
|
1997-06-20 19:17:03 +02:00
|
|
|
while ( isspace(*str)) str++;
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
if ( *str == ',' || !(*str) )
|
|
|
|
elog(WARN, "Syntax error near (=%s)", str);
|
|
|
|
|
|
|
|
start = str;
|
|
|
|
|
|
|
|
/*
|
1997-06-20 19:17:03 +02:00
|
|
|
* count chars in token's value until we hit white space or comma
|
1997-06-02 13:00:57 +02:00
|
|
|
* or end of string
|
|
|
|
*/
|
1997-06-20 19:17:03 +02:00
|
|
|
while ( *str && (! isspace(*str)) && *str != ',' )
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
|
|
|
str++;
|
|
|
|
len++;
|
|
|
|
}
|
|
|
|
|
1997-06-20 19:17:03 +02:00
|
|
|
*val = (char*) PALLOC(len + 1);
|
1997-08-12 22:16:25 +02:00
|
|
|
strNcpy (*val, start, len);
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
/* skip white spaces */
|
1997-06-20 19:17:03 +02:00
|
|
|
while ( isspace(*str)) str++;
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
if ( !(*str) )
|
|
|
|
return (NULL);
|
|
|
|
if ( *str == ',' )
|
|
|
|
return (++str);
|
|
|
|
|
|
|
|
elog(WARN, "Syntax error near (%s)", str);
|
|
|
|
|
|
|
|
return str;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
static bool parse_null(const char *value)
|
|
|
|
{
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
static bool show_null(const char *value)
|
|
|
|
{
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
static bool reset_null(const char *value)
|
|
|
|
{
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-29 06:38:58 +02:00
|
|
|
static bool parse_geqo (const char *value)
|
|
|
|
{
|
1997-06-02 13:00:57 +02:00
|
|
|
const char *rest;
|
|
|
|
char *tok, *val;
|
1997-04-29 06:38:58 +02:00
|
|
|
|
1997-06-02 13:00:57 +02:00
|
|
|
rest = get_token (&tok, &val, value);
|
|
|
|
if ( tok == NULL )
|
|
|
|
elog(WARN, "Value undefined");
|
|
|
|
|
1997-06-20 19:17:03 +02:00
|
|
|
if (( rest ) && ( *rest != '\0' ))
|
|
|
|
elog(WARN, "Unable to parse '%s'", value);
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
if ( strcasecmp (tok, "on") == 0 )
|
|
|
|
{
|
1997-06-03 08:29:31 +02:00
|
|
|
int32 geqo_rels = GEQO_RELS;
|
1997-06-02 13:00:57 +02:00
|
|
|
|
|
|
|
if ( val != NULL )
|
|
|
|
{
|
|
|
|
geqo_rels = pg_atoi (val, sizeof(int32), '\0');
|
|
|
|
if ( geqo_rels <= 1 )
|
|
|
|
elog(WARN, "Bad value for # of relations (%s)", val);
|
1997-06-20 19:17:03 +02:00
|
|
|
PFREE(val);
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-04-29 06:38:58 +02:00
|
|
|
_use_geqo_ = true;
|
1997-06-02 13:00:57 +02:00
|
|
|
_use_geqo_rels_ = geqo_rels;
|
|
|
|
}
|
|
|
|
else if ( strcasecmp (tok, "off") == 0 )
|
|
|
|
{
|
1997-06-20 19:17:03 +02:00
|
|
|
if (( val != NULL ) && ( *val != '\0' ))
|
|
|
|
elog(WARN, "%s does not allow a parameter",tok);
|
1997-04-29 06:38:58 +02:00
|
|
|
_use_geqo_ = false;
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-04-29 06:38:58 +02:00
|
|
|
else
|
1997-06-02 13:00:57 +02:00
|
|
|
elog(WARN, "Bad value for GEQO (%s)", value);
|
1997-04-29 06:38:58 +02:00
|
|
|
|
1997-06-20 19:17:03 +02:00
|
|
|
PFREE(tok);
|
1997-04-29 06:38:58 +02:00
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool show_geqo ()
|
|
|
|
{
|
|
|
|
|
|
|
|
if ( _use_geqo_ )
|
1997-06-20 19:17:03 +02:00
|
|
|
elog (NOTICE, "GEQO is ON beginning with %d relations", _use_geqo_rels_);
|
1997-04-29 06:38:58 +02:00
|
|
|
else
|
|
|
|
elog (NOTICE, "GEQO is OFF");
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool reset_geqo ()
|
|
|
|
{
|
|
|
|
|
|
|
|
#ifdef GEQO
|
|
|
|
_use_geqo_ = true;
|
|
|
|
#else
|
|
|
|
_use_geqo_ = false;
|
|
|
|
#endif
|
1997-06-02 13:00:57 +02:00
|
|
|
_use_geqo_rels_ = GEQO_RELS;
|
1997-04-29 06:38:58 +02:00
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-05-20 12:31:42 +02:00
|
|
|
static bool parse_r_plans (const char *value)
|
|
|
|
{
|
|
|
|
|
|
|
|
if ( strcasecmp (value, "on") == 0 )
|
|
|
|
_use_right_sided_plans_ = true;
|
|
|
|
else if ( strcasecmp (value, "off") == 0 )
|
|
|
|
_use_right_sided_plans_ = false;
|
|
|
|
else
|
|
|
|
elog(WARN, "Bad value for Right-sided Plans (%s)", value);
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool show_r_plans ()
|
|
|
|
{
|
|
|
|
|
|
|
|
if ( _use_right_sided_plans_ )
|
|
|
|
elog (NOTICE, "Right-sided Plans are ON");
|
|
|
|
else
|
|
|
|
elog (NOTICE, "Right-sided Plans are OFF");
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool reset_r_plans ()
|
|
|
|
{
|
|
|
|
|
|
|
|
#ifdef USE_RIGHT_SIDED_PLANS
|
|
|
|
_use_right_sided_plans_ = true;
|
|
|
|
#else
|
|
|
|
_use_right_sided_plans_ = false;
|
|
|
|
#endif
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-24 17:41:37 +02:00
|
|
|
static bool parse_cost_heap (const char *value)
|
|
|
|
{
|
|
|
|
float32 res = float4in ((char*)value);
|
|
|
|
|
|
|
|
_cpu_page_wight_ = *res;
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool show_cost_heap ()
|
|
|
|
{
|
|
|
|
|
|
|
|
elog (NOTICE, "COST_HEAP is %f", _cpu_page_wight_);
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool reset_cost_heap ()
|
|
|
|
{
|
|
|
|
_cpu_page_wight_ = _CPU_PAGE_WEIGHT_;
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool parse_cost_index (const char *value)
|
|
|
|
{
|
|
|
|
float32 res = float4in ((char*)value);
|
|
|
|
|
|
|
|
_cpu_index_page_wight_ = *res;
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool show_cost_index ()
|
|
|
|
{
|
|
|
|
|
|
|
|
elog (NOTICE, "COST_INDEX is %f", _cpu_index_page_wight_);
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool reset_cost_index ()
|
|
|
|
{
|
|
|
|
_cpu_index_page_wight_ = _CPU_INDEX_PAGE_WEIGHT_;
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
static bool parse_date(const char *value)
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
1997-06-20 19:17:03 +02:00
|
|
|
char *tok;
|
1997-04-17 15:50:57 +02:00
|
|
|
int dcnt = 0, ecnt = 0;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
|
|
|
while((value = get_token(&tok, NULL, value)) != 0)
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
1997-04-17 15:50:57 +02:00
|
|
|
/* Ugh. Somebody ought to write a table driven version -- mjl */
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
if(!strcasecmp(tok, "iso"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_ISO_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
|
|
|
}
|
|
|
|
else if(!strcasecmp(tok, "sql"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_SQL_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
|
|
|
}
|
|
|
|
else if(!strcasecmp(tok, "postgres"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
|
|
|
}
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
else if(!strncasecmp(tok, "euro", 4))
|
|
|
|
{
|
|
|
|
EuroDates = TRUE;
|
|
|
|
ecnt++;
|
|
|
|
}
|
|
|
|
else if((!strcasecmp(tok, "us"))
|
|
|
|
|| (!strncasecmp(tok, "noneuro", 7)))
|
1997-04-17 15:50:57 +02:00
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
EuroDates = FALSE;
|
1997-04-17 15:50:57 +02:00
|
|
|
ecnt++;
|
|
|
|
}
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
else if(!strcasecmp(tok, "default"))
|
1997-04-17 15:50:57 +02:00
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
|
|
|
EuroDates = FALSE;
|
1997-04-17 15:50:57 +02:00
|
|
|
ecnt++;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
1997-05-16 09:24:13 +02:00
|
|
|
elog(WARN, "Bad value for date style (%s)", tok);
|
1997-04-17 15:50:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
PFREE(tok);
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
if(dcnt > 1 || ecnt > 1)
|
|
|
|
elog(NOTICE, "Conflicting settings for date");
|
1997-06-02 13:00:57 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
return TRUE;
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
static bool show_date()
|
|
|
|
{
|
|
|
|
char buf[64];
|
|
|
|
|
1997-05-16 09:24:13 +02:00
|
|
|
strcpy( buf, "DateStyle is ");
|
|
|
|
switch (DateStyle) {
|
|
|
|
case USE_ISO_DATES:
|
|
|
|
strcat( buf, "ISO");
|
|
|
|
break;
|
|
|
|
case USE_SQL_DATES:
|
|
|
|
strcat( buf, "SQL");
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
strcat( buf, "Postgres");
|
|
|
|
break;
|
|
|
|
};
|
|
|
|
strcat( buf, " with ");
|
|
|
|
strcat( buf, ((EuroDates)? "European": "US (NonEuropean)"));
|
|
|
|
strcat( buf, " conventions");
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
|
|
|
|
elog(NOTICE, buf, NULL);
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
static bool reset_date()
|
|
|
|
{
|
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
|
|
|
EuroDates = FALSE;
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
struct VariableParsers
|
|
|
|
{
|
|
|
|
const char *name;
|
|
|
|
bool (*parser)(const char *);
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
bool (*show)();
|
|
|
|
bool (*reset)();
|
1997-04-17 15:50:57 +02:00
|
|
|
} VariableParsers[] =
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
{ "datestyle", parse_date, show_date, reset_date },
|
|
|
|
{ "timezone", parse_null, show_null, reset_null },
|
1997-04-24 17:41:37 +02:00
|
|
|
{ "cost_heap", parse_cost_heap,
|
|
|
|
show_cost_heap, reset_cost_heap },
|
|
|
|
{ "cost_index", parse_cost_index,
|
|
|
|
show_cost_index, reset_cost_index },
|
1997-04-29 06:38:58 +02:00
|
|
|
{ "geqo", parse_geqo, show_geqo, reset_geqo },
|
1997-05-20 12:31:42 +02:00
|
|
|
{ "r_plans", parse_r_plans, show_r_plans, reset_r_plans },
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
{ NULL, NULL, NULL }
|
1997-04-17 15:50:57 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-04-02 20:24:52 +02:00
|
|
|
bool SetPGVariable(const char *name, const char *value)
|
1997-03-25 10:44:00 +01:00
|
|
|
{
|
1997-04-17 15:50:57 +02:00
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
for(vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if(!strcasecmp(vp->name, name))
|
|
|
|
return (vp->parser)(value);
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
1997-04-02 20:24:52 +02:00
|
|
|
|
1997-03-25 10:44:00 +01:00
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
bool GetPGVariable(const char *name)
|
1997-03-25 10:44:00 +01:00
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
for(vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if(!strcasecmp(vp->name, name))
|
|
|
|
return (vp->show)();
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
|
|
|
|
|
|
|
return TRUE;
|
1997-03-25 10:44:00 +01:00
|
|
|
}
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
bool ResetPGVariable(const char *name)
|
|
|
|
{
|
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
for(vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if(!strcasecmp(vp->name, name))
|
|
|
|
return (vp->reset)();
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|