Re: DataBrowser bug: Primary Key contains an ampersand

[Gianluigi <gradobag@xxxxxxxxxxx>]

Il 21/11/24 11:31, BB ha scritto:
> On 21/11/24 12:06 am, Gianluigi wrote:
> > Il 20/11/24 04:57, BB ha scritto:
> > > If the primary key of the table is a text column (string) and a record's
> > > PK field contains an ampersand, e.g. "A&E" then the record is not saved
> > > after editting other columns.
> > >
> > > b
> >
> > I'm no database expert, far from it, but I don't think putting an
> > ampersand in a primary key is a good idea.
> > If it is not possible to replace the ampersand through the code it is
> > better to add a serial key to the table.
> >
> > Regards
> > Gianluigi
> Not so, Gianluigi. It is a perfectly ordinary and valid character and is
> treated as such by the dbms. The record is perfectly editable and
> saveable using ordinary code. It is just the*DataBrowser control* that
> exhibits this defect.
>
> (and as for surrogate keys, dont get me started up. 😁 Codds rules, OK!)
>
> b

For the love of God, I have no intention of discussing Codd's rules, as
I said I'm not up to it. I had only read (but I don't remember when or
where) that the ampersand could cause problems if inserted in a primary
key. This is why I suggested avoiding it.

Regards
Gianluigi