...- 100 = 10 bytes.
Page overhead(what always gets sent) = row 1 - size for 1 row i.e. 100 - 10 = 90 bytes.
so if you show 200 rows you will need 200 * 10 = 2000 bytes + 90 bytes overhead = 2090 bytes
Grossly simple but add on the HTTP headers (say 200 bytes max as overhead) would give you 2000...
$5,000 per month sounds like a lot of money. Have you considered hosting in the cloud?. I'm into the Amazon offering at the momemt.
They run MySQL instances (which they fully manage) and Oracle as well.
Check out http://aws.amazon.com/amis/Sun-Microsystems?browse=1 which lists some Solaris...
Excel is used for some interesting things these days not just simple spreadsheets.
Have a look at http://phpexcel.codeplex.com/ which might be of interest.
I havn't got mysql on my local machine but I think when you start the terminal monitor it tells you the version, and I think once in the system variables might give a clue
Have you tried switching on ODBC tracing to see what's been sent and recieved rom mysql.
Actualy can you give a bit more detail?, for example are you using VFP as a front end to Mysql?.
I've never used foxpro so have no idea what's going.
The indexthing is funny as you often get issues with the...
I would attack the issue like this:
When ever an image needs to be stored create a surrogate key consisting of the logged in user name + the image name e.g. fredJennyonthelawn.jpg
Create a hash of this key.
Need to stop here, assuming we have 10 web servers the images need to be spread across...
No worries.
This is an important issue for dev's and the architecture of any given site I think. For static images like logos yes hold them localy but for images that are uploaded for shoping carts, photo sites etc, the issues of durability, scale, accessability and caching need addressing...
I did say caching might be an issue, When I send images I give it an expirary date well into the future so it never goes back to the server, If I change the image I change it's name so a fresh copy is sent. PC will eventualy delete the unused image.
Check out yahoo dev tips on this technique.
Some good points Steve, security and image tampering is an issue. M$ share point holds everything in SQLServer (or even access) but that includes word docs and spreadsheets, they argue that physical security is better with with DB's and they have an incremental backup solution to keep dumps...
I disagre with Phil (ad I always do when this question comes up). I think storing images in the file system stops the site from scaling as without some extra logic or software you are limited to one server.
What I would recomend these days is to look as the Amazon S3 service to store images...
I think you are wanting to implement a rich user interface be it in a browser or some kind of fat client. For a fat client such as Access you have a lot of power at your fingertips, under a browser you are really needing to go down the Ajax route perhaps using jQuery. All of which will be new...
I guess M$ dev's think MySql is limited because it doesn't have a humongous syntax set way beyond the normal CRUD kind of stuff SQL is usually aimed at. Have a look at http://blogs.msdn.com/b/sqlazure/archive/2011/04/05/10149777.aspx where MySQL was rejected by old time users of it because it...
Justin:
i would have thought that if no order is specified the strorage engine would just read the table serially rather than read the index and then key into the table. On a large table with an untidy index this would lead to more i/o than really needed. I think to assume an order will lead to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.