Name clash in tables with newest release

[sweigert]

Hi,

I was upgrading to the latest release but I get an error in the generated code. It is related to how the variables are named in the generated models since it generated an error variable for the unique constraints which seems to follow the naming pattern <TableName>Errors.
But if you actually have a table, called device_errors it will also translate to DeviceErrors.

Here is a minimal example:

CREATE TABLE devices (
  id UUID,
  id2 UUID,
  PRIMARY KEY (id)
);

CREATE TABLE device_errors (
  id UUID,
  PRIMARY KEY (id)
);

ALTER TABLE devices ADD CONSTRAINT unique_devices UNIQUE (id, id2);

The generated code cannot compile since DeviceErrors will be defined multiple times.

Btw, I am really enjoying bob. Thanks for your work!

[stephenafamo]

Not good 😬 . I'll think of some ideas to prevent this in the future.

Temporarily, consider adding an alias for device_errors so that it is generated with a different name.