1052 Column 'is_deleted' in where clause is ambiguous

Topic: 1052 Column 'is_deleted' in where clause is ambiguous (Read 2547 times) previous topic - next topic

1052 Column 'is_deleted' in where clause is ambiguous

May 06, 2020, 12:40:31 PM

Dear Guys,

I am using Classic 2.7.3 and i'm trying to join tables with "Record SoftDelete" fields but I get this error below when viewing the list

Code: [Select]

1052 Column 'is_deleted' in where clause is ambiguous

Thanks,

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #1 – May 06, 2020, 03:34:53 PM

@jp26198926‍ please add table name to the fields to differentiate them.
E.g table1.is_deleted, table2.is_deleted

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #2 – May 06, 2020, 08:02:38 PM

Hi Willvin,

Thanks for your reply, may I know where can i manually edit the query?
Please see attached screenshot, i believe the join query is okay.

https://drive.google.com/file/d/1rYouYV6cfUO2RD-_f0Cuak18zro9Ddnv/view?usp=sharing

Thanks,

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #3 – May 07, 2020, 12:19:46 PM

@jp26198926‍ after configuring the join please unselect duplicate field from the list of fields that appears on the list page you are working on.

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #4 – May 08, 2020, 02:55:06 AM

Hi Willvin,

I tried that one already but no luck, see below screenshot.
https://drive.google.com/file/d/14_dVgR9FFc3jQ14Dx0fujJbiqs-Nf0uo/view?usp=sharing

Thanks,

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #5 – May 08, 2020, 04:26:25 AM

Hi Willvin,

I was able to override the error by manually editing the __construct method of the page controller, see attached screenshot.
But ofcourse this is not a convenient way since if i will do re publish again thru phprad gui the edited code will be overwritten.

https://drive.google.com/file/d/1-DiDjEFt3qRjkS9kpITi7wSfD7sXtt3-/view?usp=sharing

Thanks,

Re: 1052 Column 'is_deleted' in where clause is ambiguous

Reply #6 – May 09, 2020, 07:57:43 PM

Thanks for this insight. We will surely implement it.