Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Date: Fri, 2 Sep 2016 05:01:58 +0000 (UTC)
From: Daniel Webster <dwebst04@yahoo.com.au.INVALID>
Reply-To: Daniel Webster <dwebst04@yahoo.com.au>
To: "users@flex.apache.org" <users@flex.apache.org>
Message-ID: <1744565477.191074.1472792518718@mail.yahoo.com>
In-Reply-To: <1472259029471-13415.post@n4.nabble.com>
References: <1472259029471-13415.post@n4.nabble.com>
Subject: Re: Downloading Large Amounts of Data from Database
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_191073_981208597.1472792518712"
archived-at: Fri, 02 Sep 2016 05:02:18 -0000

------=_Part_191073_981208597.1472792518712
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Bill,
Not sure how much this will help but you can reduce the size of the meta da=
ta or variable names being transferred.On the server side when preparing th=
e data to return to the client (or via SQL aliases), you can change all of =
the variable names in each row to something very short instead (e.g. "first=
_name" becomes "fn", "comment" becomes "cm" etc). This can really reduce th=
e amount of data returned, especially if there are a lot of columns.Or, ret=
urn each row as an indexed array only so there are no variable names at all=
 to transfer along with the data.In the client you will then have to map th=
em back to the original names.
I have a habit of returning the same database column names as the variable =
names but I try to rename/alias them if I have time.

Here's an example in json:

[=C2=A0=C2=A0=C2=A0 {"id": 1, "person_name": "Jim", "address": "123 test ro=
ad"},=C2=A0=C2=A0=C2=A0 {"id": 2, "person_name": "Phil", "address": "63 tes=
t road"}]
(141 bytes)


now becomes
[=C2=A0=C2=A0=C2=A0 {"id": 1, "pn": "Jim", "ad": "123 test road"},=C2=A0=C2=
=A0=C2=A0 {"id": 2, "pn": "Phil", "ad": "63 test road"}](111 bytes ~ 22% re=
duction)


Daniel


      From: bilbosax <waspence41@comcast.net>
 To: users@flex.apache.org=20
 Sent: Saturday, 27 August 2016, 10:50
 Subject: Downloading Large Amounts of Data from Database
  =20
I am running into an issue that I believe is going to take some creative
problem solving.=C2=A0 I have created a service to download large amounts o=
f data
from a MySQL database, at least 50k records, but the app always times out
before all of the data can be downloaded.=C2=A0 Has anyone ever run into th=
is
problem and found a solution? I don't know if there is a way to download
smaller section of the database at a time and add it all together.=20

Thanks,
Bill


--
View this message in context: http://apache-flex-users.2333346.n4.nabble.co=
m/Downloading-Large-Amounts-of-Data-from-Database-tp13415.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.


  =20
------=_Part_191073_981208597.1472792518712--