[showstopping deadly bug] 14.1 can't save record without

Michael Larue (3/23/14 7:50AM)
Lee Hinde (3/24/14 10:15AM)
Joshua Fletcher (3/25/14 6:16PM)
Michael Larue (3/27/14 3:13PM)


Michael Larue (3/23/14 7:50 AM)

primary key

Sunday, March 23, 2014 at 6:55:07 AM

Version 14.1 on Mac 10.9.2: it appears you are now REQUIRED by 4D to
have a designated Primary Key on every table?

It looks like they just added a new feature that prevents you from
SAVING a record to a table where the Primary Key has not been defined,
even if you designate the table not to be ?=80újournalized?=80ù.

Any way to disable this?

I tried the following:

1) In the Primary Key manager, I designated a table NOT to have a
primary key (or not journalized).

2) In the Database Settings -> Backup -> Configuration, the ?=80úUse
Log
File?=80ù is unchecked.

3) I tried executing the following snippet of SQL code:

Begin SQL
=A0ALTER TABLE table_name DISABLE LOG
End SQL

Needless to say, none of these solved the problem. I cannot save a
record to a table that doesn?=80ôt have the PK assigned; I get an
error
message and 4D doesn?=80ôt let me save the record.

Note that version 14.0 did not have this restriction; I was able to
save the record (and if I go back to 14.0, it allows me to save).

Help! What do I have to do to disable this ?=80úfeature?=80ù?
(Other than
creating and populating a PK field?)

(This is not to start another thread on the importance of primary
keys. Yes, I know having primary keys is important. You?=80ôre not
allowed
to wear your ?=80úprogrammer?=80ù badge if you ever have a table
without one.
However, I didn?=80ôt realize that this was going to be _enforced_
in such
a draconian way. I guess version 14.2 will kindly help you out by
simply deleting all tables without them...)

Also, I notice that clicking on the little ?=80úkey?=80ù icon in
the Structure
Editor (to bring up the Primary Key manager window) doesn?=80ôt
allow me
to make any edits. It only displays the list of tables, and what the
primary keys are (or not), but there?=80ôs no way to change anything
from
this window. I tried in both version 14 and 14.1, and both of them
appear to be ?=80úlocked?=80ù?=80îyou only get one shot at
this when you convert
the first time, and then the PK manager window is just informational.

Thanks for any help; really need to solve this for being able to
update.

Michael Larue

Lee Hinde (3/24/14 10:15 AM)

primary key

<CA+ePoMy6K8o3v6j-GJ8J9704Jw4AZh-ESgtD5yyMHrFZX+OYHA@...

I'm getting similar behavior, but I've not debugged as exhaustively as
you
have.

On Sat, Mar 22, 2014 at 11:50 PM, Michael Larue <larue@...
wrote:

color><param>00000,0000,DDEE/param>SSunday, March 23, 2014 at 6:55:07
AM

Version 14.1 on Mac 10.9.2: it appears you are now REQUIRED by 4D to
have
a designated Primary Key on every table?

It looks like they just added a new feature that prevents you from
SAVING
a record to a table where the Primary Key has not been defined, even
if you
designate the table not to be &igrave;journalized&icirc;.

Any way to disable this?

I tried the following:

1) In the Primary Key manager, I designated a table NOT to have a
primary
key (or not journalized).

2) In the Database Settings -> Backup -> Configuration, the &igrave;Use Log
File&icirc;
is unchecked.

3) I tried executing the following snippet of SQL code:

Begin SQL
?ALTER TABLE table_name DISABLE LOG
End SQL

Needless to say, none of these solved the problem. I cannot save a
record
to a table that doesn&iacute;t have the PK assigned; I get an error message
and 4D
doesn&iacute;t let me save the record.

Note that version 14.0 did not have this restriction; I was able to
save
the record (and if I go back to 14.0, it allows me to save).

Help! What do I have to do to disable this &igrave;feature&icirc;? (Other than
creating
and populating a PK field?)

(This is not to start another thread on the importance of primary keys.
Yes, I know having primary keys is important. You&iacute;re not allowed to
wear
your &igrave;programmer&icirc; badge if you ever have a table without one.
However, I
didn&iacute;t realize that this was going to be _enforced_ in such a
draconian
way. I guess version 14.2 will kindly help you out by simply deleting
all
tables without them...)

Also, I notice that clicking on the little &igrave;key&icirc; icon in the
Structure
Editor (to bring up the Primary Key manager window) doesn&iacute;t allow me
to
make any edits. It only displays the list of tables, and what the
primary
keys are (or not), but there&iacute;s no way to change anything from this
window.
I tried in both version 14 and 14.1, and both of them appear to be
&igrave;locked&icirc;&oacute;you only get one shot at this when you convert the first
time, and
then the PK manager window is just informational.

Thanks for any help; really need to solve this for being able to
update.

Michael Larue

/color>

Joshua Fletcher (3/25/14 6:16 PM)

primary key

Guys please contact Technical Support directly if you have not
already. I
certainly appreciate taking the time to file a bug report but if
there's
an issue blocking you from using 4D you need to contact TS directly
IMHO.

(in case it doesn't make sense: bug reports don't go directly to TS)

Thanks!

-Josh

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

Michael Larue (3/27/14 3:13 PM)

primary key

Thursday, March 27, 2014 at 7:52:37 AM

Hi,

Just wanted to follow up on this; not sure if I'm allowed to reveal
this (the info came from a private message), but I understand 4D has
recognized this as a bug and is working on a fix.

So if anyone else has run into this problem (it happens under certain
conditions, of which my database qualifies), hang tight, help is on
the way.

THANK YOU 4D!!! Looking forward to 14.2...

Michael Larue

Reply to this message

Summary created 3/27/14 at 10:48AM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com