Smalltalk › Instantiations

Simpler database result structure

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Carl Gundel-2

Simpler database result structure

For performance reasons, I wonder if the VA database framework has a way of returning simply a collection of rows, which are just arrays with simpler data types in them. My application was originally designed to consume such a structure, and now I have to incur the expense of the existing more rich result, and then also convert it into the simple collection of row collections structure. It is quite a performance problem.

I hope my explanation is clear.

-Carl Gundel

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/groups/opt_out.

jtuchel

Re: Simpler database result structure

Carl,

Without using an Image to test, I'd say what the VA DB framework returns from SQL results is exactly what you describe: a collection of rows, each being or having a similar api as a Dictionary.

What exactly do you do to get results from the db and what does the result look like?

Joachim

Am Montag, 15. Juli 2013 21:57:12 UTC+2 schrieb Carl Gundel:

For performance reasons, I wonder if the VA database framework has a way of returning simply a collection of rows, which are just arrays with simpler data types in them. My application was originally designed to consume such a structure, and now I have to incur the expense of the existing more rich result, and then also convert it into the simple collection of row collections structure. It is quite a performance problem.

I hope my explanation is clear.

-Carl Gundel

Carl Gundel-2

Re: Simpler database result structure

Joachim,

I need each row to be just an array of values. Too much expense to build an a collection of complex dictionary-like objects for each row and then strip it back down again so that my app can use it. The existing VisualSmalltalk Enterprise version of the application loads from the database 5x faster than under VA.

-Carl

On Tuesday, July 16, 2013 12:08:28 AM UTC-4, [hidden email] wrote:

Carl,

Without using an Image to test, I'd say what the VA DB framework returns from SQL results is exactly what you describe: a collection of rows, each being or having a similar api as a Dictionary.
What exactly do you do to get results from the db and what does the result look like?

Joachim

Am Montag, 15. Juli 2013 21:57:12 UTC+2 schrieb Carl Gundel:
For performance reasons, I wonder if the VA database framework has a way of returning simply a collection of rows, which are just arrays with simpler data types in them. My application was originally designed to consume such a structure, and now I have to incur the expense of the existing more rich result, and then also convert it into the simple collection of row collections structure. It is quite a performance problem.

I hope my explanation is clear.

-Carl Gundel

Wayne Johnston

Re: Simpler database result structure

So you would assume the array is in the same order as the columns are defined in the database?

Carl Gundel-2

Re: Simpler database result structure

In our application we specify which columns we want when we select. The results are in the order they are specified.

-Carl

On Sunday, July 21, 2013 8:26:18 PM UTC-4, Wayne Johnston wrote:

So you would assume the array is in the same order as the columns are defined in the database?

jtuchel

Re: Simpler database result structure

I guess the problem here is that, ignoring the fact that select * should be avoided generally, it is still possible, and so the code would have to determine whether it can assume the code that issued a query knows which columns to expect or not and then return either the dictionary structure or an array.

To be honest, that doesn't sound like a nice solution to me.

Of course you could also introduce a switch.

Joachim

Am Montag, 22. Juli 2013 21:51:55 UTC+2 schrieb Carl Gundel:

In our application we specify which columns we want when we select. The results are in the order they are specified.

-Carl

On Sunday, July 21, 2013 8:26:18 PM UTC-4, Wayne Johnston wrote:
So you would assume the array is in the same order as the columns are defined in the database?