* Konstantin Osipov [09/02/05 03:35]:
> > People are using MySQL because it's different and can satisfy their
> > needs. Standards are useful, but not important for our current or
> > future users. Getting the job done and not having downtime, even when
> > upgrading, that is important!
Hear, Mo
* Michael Widenius [09/02/03 19:24]:
> Konstantin> Monty, I disagree with this statement. Our current users use the
> Konstantin> current versions of the server. It's a separate question of what
> Konstantin> support we're willing to give them and for how long.
> Konstantin> In the new versions w
Hi!
> "Konstantin" == Konstantin Osipov writes:
Konstantin> * Michael Widenius [09/01/30 14:53]:
>> Its more important that we don't break things for current users than
>> try to be concerned about possible wrong usage that no one seams to do
>> or find important enough to complain about.
>IMO, offering a variety of input formats just creates one big mess.
>How often have you read some date notation and wondered which format was
>used - if all values are in the 1 to 12 range, you have to guess.
>
[JS] I agree 100%. I have to deal with dates from all over the world, and I
often have
Hi!
Konstantin Osipov wrote:
> * Michael Widenius [09/01/30 14:53]:
>
>> Its more important that we don't break things for current users than
>> try to be concerned about possible wrong usage that no one seams to do
>> or find important enough to complain about.
>
> Monty, I disagree with this
* Michael Widenius [09/01/30 14:53]:
> Its more important that we don't break things for current users than
> try to be concerned about possible wrong usage that no one seams to do
> or find important enough to complain about.
Monty, I disagree with this statement. Our current users use the
curr
Michael Widenius wrote:
> Bernt> We have a Norwgeian word for this "helpfullness":
> "bjørnetjeneste", but Bernt> I'm not sure what the english idiom would
> be.
A disservice. In German Bärendienst.
/Per Jessen, Zürich
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/m
Hi!
> "Bernt" == Bernt M Johnsen writes:
> Michael Widenius wrote (2009-01-24 02:07:54):
>> As Dmitri pointed out, we shouldn't deprecate '.' as substitute for
>> dates.
>>
>> Another things is that we should stop making decisions about
>> incompatible changes without listening
Hi!
> "Roy" == Roy Lyseng writes:
>> The question here is how PostgreSQL and ANSI does this and also what
>> is the logical interpretation of the number.
Roy> ISO 9075 (ANSI SQL) is very strict about this. It only allows TIME
Roy> literals with 3 or 4 digit groups, and it only allows th
Hi Monty,
Michael Widenius wrote:
> Hi!
>
>> "Peter" == Peter Gulutzan writes:
>
> Peter> Hi all,
> Peter> On 01/15/2009 03:11 PM Peter Gulutzan wrote:
>
>>> For a TIME or DATETIME or TIMESTAMP literal, one can use
>>> '.' instead of ':' and one can skip leading fields. For example:
>>> IN
Michael Widenius wrote:
Hi!
"Peter" == Peter Gulutzan writes:
Peter> Hi all,
Peter> On 01/15/2009 03:11 PM Peter Gulutzan wrote:
For a TIME or DATETIME or TIMESTAMP literal, one can use
'.' instead of ':' and one can skip leading fields. For example:
INSERT INTO t (datetime_column) VALUE
11 matches
Mail list logo
