• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
jeff8j

MySQL num rows

8 posts in this topic

I created my own mysql client connection following their protocol
http://forge.mysql.com/wiki/MySQL_Internals_ClientServer_Protocol

I can query just fine now and its working great but I am trying to find a way to implement a mysql_num_rows and cannot find a way todo it without first getting all the rows. What I would like is to get the number first and I dont want to have to store several thousand rows before I know how much I will be dealing with.

I have read and reread the protocol but cant find anything could someone help point me in a direction or tell me that the only way would be to get the rows first? Thanks
0

Share this post


Link to post
Share on other sites
Just a stab in the dark... would the COUNT function help you?
0

Share this post


Link to post
Share on other sites
Generally the database does not know how may rows will be returned unless you do a count(*) or actually fetch all of the rows. In many cases, the DB does not need to build the whole result set before it can start outputting rows to the client, and so it will output rows as you fetch them in more of a streaming fashion. This avoids doing any unnecessary work if you cancel the query before fetching all available results, and also avoids having to keep results in a temporary area until you fetch them.

Certain queries which involve sorting/grouping etc may require the whole result set to be built before it can output anything, in which case fetching the first batch of rows will be slow, and fetching subsequent batches will be faster as all of the heavy lifting has already been done.
1

Share this post


Link to post
Share on other sites
Thank you WavyVirus. That makes sense and I guess you wouldnt want it to get the result set first so I can complain lol ill just have to store everything and count it thats fine.
0

Share this post


Link to post
Share on other sites
Oh and to taby The Count function would either a have to perform 2 queries or b modify the query to have a count in it then strip it from the result set both could be done but wouldnt be pretty.
0

Share this post


Link to post
Share on other sites
[quote name='jeff8j' timestamp='1342706299' post='4960936']
Oh and to taby The Count function would either a have to perform 2 queries or b modify the query to have a count in it then strip it from the result set both could be done but wouldnt be pretty.
[/quote]

Yep, that's the point of count -- "find a way to implement a mysql_num_rows [snip] without first getting all the rows". Edited by taby
0

Share this post


Link to post
Share on other sites
I think ill just store the result set in memory rather than do 2 queries or try to modify the queries and result fields on the fly. Thank You
0

Share this post


Link to post
Share on other sites
That seems sensible (assuming you really need to know the count at all). You cannot guarantee that the count will be the same if you issue two queries (unless you use something like "serializable" isolation level, but I think that has major locking implications in mysql). Fudging the query to somehow return a count would be really ugly as well.
0

Share this post


Link to post
Share on other sites
My opinion: The fact that you want a count means that you're not doing proper stream processing of your data.
Perhaps a more efficient way is to find a way to write the application layer without count, instead.

For select count() to return the number of rows that a later select will return, your transaction isolation level needs to be "repeatable-read" or better. However, any isolation level below "serializable" is not fully transaction compliant. If you're using MySQL for an online transaction database, you should be using "serializable." Also, when benchmarking against other databases, you should probably be using this isolation level.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0