Experiences with 14.1 - ready for deployment?

Peter Lerch (5/1/14 4:58AM)
Joshua Fletcher (5/2/14 9:14PM)


Peter Lerch (5/1/14 4:58 AM)

jlbrown wrote
color><param>00000,0000,DDEE/param>NNow that 14.1 is out with lots of
bug fixes, I?=A2?=82=E2&Ntilde;m interested to hear of
people?=A2?=82=E2&Ntilde;s experiences? Is it stable enough for use
yet?
...
Anything to be wary of? Has anyone encountered any show-stoppers?
/color>
We are going life with the first site on Monday. There are several
annoying
bugs, but no real show-stoppers. We found workarounds for all
problems. Did
you check the list of open issues already (especially ACI0087579)?

Peter

--
View this message in context:

http://4d.1045681.n5.nabble.com/Experiences-with-14-1-ready-for-deployment
-tp5730117p5730123.html
Sent from the 4D Tech mailing list archive at Nabble.com.

Joshua Fletcher (5/2/14 9:14 PM)

color><param>00000,0000,DDEE/param>AAlthough you mention you've done
the stuff with PK, watch out for any
table
without one. If you try to save the record while in a transaction,
you'll
get an error message and can't save. (That's a show stopper for our
database for 14.1.)
/color>

Though this has already been fixed internally, I'm wondering how this
is
that a showstopper? =A0What's *wrong* with defining a primary key?
=A0I.e.
why
doesn't the table already have a Primary Key defined? =A0Do you
really
plan
to leave it that way? =A0I would expect that if the table is
important
enough to be involved in a transaction, it should also be journaled.
But
you can't journal without a primary key. =A0Curious as to why you
think
it's
important to not have a primary key defined?

Thanks!

-Josh

--
Josh Fletcher
Technical Account Manager
4D, Inc.

Reply to this message

Summary created 5/2/14 at 3:56PM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com