Re: ds.Table.query() field not available
> On Mar 10, 2020, at 9:17 PM, Sannyasin Siddhanathaswami via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > for instance, could it be that the table does not have a primary key? Changing something in structure and not having primary key might cause the issue. Milan ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: ds.Table.query() field not available
You were not hallucinating. When a field name is changed in the structure, the app must be restarted for the change to be recognized. Keith - CDI > On Mar 10, 2020, at 3:17 PM, Sannyasin Siddhanathaswami via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Ok. I guess I was hallucinating or something. It works today with one > exception. If I change the name of a field (to remove spaces in field > names…..), the new field name doesn’t work in an orda query. I get this error: > > The "Account_Name" attribute cannot be found in The "Deposits" datastore class > > This is where I have to reboot the server as the only way to update the > datastore, right? > > Thanks for the list of possible errors and troubleshooting options Miyako. I > will use them! > > Sannyasin Siddhanathaswami > On Mar 9, 2020, 6:47 PM -1000, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com>, wrote: > Hello, > > When I do a ds.Table.query() using a field/attribute of a non-indexed field, > I get an error. > > that has not been my experience. > v18, Client/Server, non-indexed field, ORDA query has always worked just fine. > > --- > > are sure definitely sure that indexing is causing the problem? > > for instance, could it be that the table does not have a primary key? > what is the field type? is it an object? > what does the query string look like? > does it include "linked" queries? (e.g. attr[a].attr = :1 and attr[a].prop = > :2) > can you reproduce the problem on a fresh DB? > > Of course, I can add an index, but then I seem to have restart the server for > it to work. This is super inconvenient, obviously and in may cases not > possible at that moment. Is there a command to run that reloads whatever list > the ds.Table.query() uses to find field/attributes? Or Should I just index > all fields? What do you all do? > > ** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** > ** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: ds.Table.query() field not available
Ok. I guess I was hallucinating or something. It works today with one exception. If I change the name of a field (to remove spaces in field names…..), the new field name doesn’t work in an orda query. I get this error: The "Account_Name" attribute cannot be found in The "Deposits" datastore class This is where I have to reboot the server as the only way to update the datastore, right? Thanks for the list of possible errors and troubleshooting options Miyako. I will use them! Sannyasin Siddhanathaswami On Mar 9, 2020, 6:47 PM -1000, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com>, wrote: Hello, When I do a ds.Table.query() using a field/attribute of a non-indexed field, I get an error. that has not been my experience. v18, Client/Server, non-indexed field, ORDA query has always worked just fine. --- are sure definitely sure that indexing is causing the problem? for instance, could it be that the table does not have a primary key? what is the field type? is it an object? what does the query string look like? does it include "linked" queries? (e.g. attr[a].attr = :1 and attr[a].prop = :2) can you reproduce the problem on a fresh DB? Of course, I can add an index, but then I seem to have restart the server for it to work. This is super inconvenient, obviously and in may cases not possible at that moment. Is there a command to run that reloads whatever list the ds.Table.query() uses to find field/attributes? Or Should I just index all fields? What do you all do? ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com ** ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: ds.Table.query() field not available
Never seen this. Remember everything in ORDA is case sensitive. > On Mar 9, 2020, at 10:08 PM, Sannyasin Siddhanathaswami via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > When I do a ds.Table.query() using a field/attribute of a non-indexed field, > I get an error. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: ds.Table.query() field not available
Hello, When I do a ds.Table.query() using a field/attribute of a non-indexed field, I get an error. that has not been my experience. v18, Client/Server, non-indexed field, ORDA query has always worked just fine. --- are sure definitely sure that indexing is causing the problem? for instance, could it be that the table does not have a primary key? what is the field type? is it an object? what does the query string look like? does it include "linked" queries? (e.g. attr[a].attr = :1 and attr[a].prop = :2) can you reproduce the problem on a fresh DB? Of course, I can add an index, but then I seem to have restart the server for it to work. This is super inconvenient, obviously and in may cases not possible at that moment. Is there a command to run that reloads whatever list the ds.Table.query() uses to find field/attributes? Or Should I just index all fields? What do you all do? ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
