Sync Meteor.publish() with callback function


I’m Using Meteor.publish() on the server side to fetch data from the Mysql Database Table using the numtel mysql package.

But somehow I’m unable to sync the calls on the client side.

var selectedData = new MysqlSubscription('selectData');

//perform some calculations with the above retrieved data
function calculateData(dataset) {
//calculations logic.......

var liveDb = new LiveMysql({ host: 'localhost', post: 3306, user: 'root', password: 'root', database: 'development_data' });

Meteor.publish('selectData', function() {
     return'select * from data_table', [{
            table: "data_table"

Since there is no callback for the above publish function I’m unable to sync it on the client side.
As the retrieval of the data from the db takes time the calculateData() function is executed with the empty data and throws an error.

I’ve also used the above select statement within the Meteor.methods() as it supports callback function but it’s failing to execute with the Select statement while it works fine with the Insert , Update & Delete.

Please help…


I would try something like:

Template.myTemplate.onCreated(function () {
  let self = this;
  self.autorun(function () {
    let selectDataSub = self.subscribe('selectData');
    if (selectDataSub.ready()) {


It’s been a while since I used the numtel:mysql package, but the MysqlSubscription returns an object which allows you to reactively respond to the results of the query. In other words, you do not get a callback. Instead you need to use the reactive method within a reactive context (like a template helper) to get the data (this could be an autorun if you need the data in something other than a helper).

So, outside of a template, something like:

import { Tracker } from 'meteor/tracker';

const selectedData = new MysqlSubscription('selectData');

Tracker.autorun(() => {

function calculateData(dataset) {
  // calculations logic.......

However, you should be aware that the autorun will rerun whenever the result set changes (including from its initial, undefined state), so your calculateData function needs to be able to cope with this.