Replies

• ghherlin Posts: 20Questions: 3Answers: 0

  August 2023

  Hold your horses...

  It turns out that, in searching for the cause of an aborted GET, I disabled the abort that performs this inhibition...

  My fault, then.

  But I still think that setting up the URL for a send that never gets called, and using the abort to this end isn't very pretty.

  Fixing the root cause would be better.
  Would you agree?
• ghherlin Posts: 20Questions: 3Answers: 0

  August 2023

  It turns out, finally, that the problem still exists: this is because sometimes the datatable is initialised but never filled (by a server call) because it is known to be empty.

  In that case, the GET is not aborted and the datatabel receives the HTML, with the expected, unwanted, result.

  I suppose I could make an endpoint to return empty data, but that reminds me of bandaging a wooden leg.

  Would it be possible to fix this?
• ghherlin Posts: 20Questions: 3Answers: 0

  August 2023

  And also, relying on a race condition to fix a problem is IMHO not good.
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  August 2023

  Hi,

  I'm quite confused as to why you don't want the ajax option to send its initial data fetch request. The answer is that you can stop it using the preXhr something like this:

  $('#example')
    .one('preXhr.dt', function () {
      return false;
    })
    .DataTable({
      ajax: '...'
    });
  

  However, I don't understand why you would want to do that? Perhaps you can link to a test case showing the underlying issue please?

  Allan
• ghherlin Posts: 20Questions: 3Answers: 0

  August 2023

  A proposal to achieve this:
  modify line 14 of this utility function as follows, adding a test for an URL:

  /**
       * Detect the data source being used for the table. Used to simplify the code
       * a little (ajax) and to make it compress a little smaller.
       *
       *  @param {object} settings dataTables settings object
       *  @returns {string} Data source
       *  @memberof DataTable#oApi
       */
      function _fnDataSource ( settings )
      {
          if ( settings.oFeatures.bServerSide ) {
              return 'ssp';
          }
          else if ( (settings.ajax && settings.ajax.url != null) || settings.sAjaxSource ) {
              return 'ajax';
          }
          return 'dom';
      }
  

  In my version of datatables.js, the function starts at line 96436.
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  August 2023

  I'm still not clear on the use case. Before I make any changes I'd like to understand why it is needed. I don't understand why you would specify the ajax option if you aren't using the built in Ajax?

  Allan
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  August 2023

  I've been looking over our bug list today and one caught my attention which I think is basically asking the same as your own. Don't make an ajax request if the url is given as an empty string. Then, later the DataTable can be populated using ajax.url().load() (presumably based on user data).

  I've committed that into my DataTables 2 branch and it will be included in DataTables 2.

  Allan