Hi,
...
> key reference). Isn't then the query valid for those tuples which do not
> result in a violation of the referential integrity test? Shouldn't those
> tuples in a be deleted?
The "all or nothing" approach causes this. And _here_ **I think** its
correct behaviour. (IMHO user and backend
Hi,
...
> LC_NUMERIC and LC_TIME
...
> The timeofday() make output via strftime() if you set LC_ALL, a query
> like: select timeofday()::timestamp;
Actually *I would* expect it to return a localized string. But then again I
always expect BE to use '.' as decimal point ( I must be damaged :-/ ).
Hi,
Im still trying to figure out how postgre does things. And Im clueless.
Somewhere inside the backend there must occur a compare between "column" and
'string'. But where (and how)?
Ive been messing around with the source code in Linux, but with no success.
// Jarmo
PS. dbinit failed when I
Hi,
The subject says it all.
I want to mess up the backend so...
Do I need lex or flex?
Do I need autoconf (does it even exist for Windows)?
Do I need Cygnus?
Do I need any other aditional packages?
Does it compile with VC6?
Does nmake do or do I need gnu make?
Or is it easier to play around
...
> > Is there a way to make postgre insensitive about field name cases?
> >
> > Like
"initdb --fields-are-case-insensitive --compares-are-case-insensitive"
...
> The main problem I see with case-insensitivity is the fact that there
> are always more than one way to do it, as it depends on char
Hi,
Is there a way to make postgre insensitive about field name cases?
Like "initdb --fields-are-case-insensitive --compares-are-case-insensitive"
Yes I know about "CaseIsKept" and CaseIsNotKept (note the quotes). But that
gives me more trouble than it solves. And what about "case insensitive f
