BlitzData 1.3 RC9

Community Forums/Showcase/BlitzData 1.3 RC9

Kanati(Posted 2004) [#1]
Dammit... Wayne stuck a bug in my ear that wouldn't go away.

Added:

BD_SetQueryTimeout()
BD_GetQueryTimeout()

Significantly changed the way I was returning the dataset.

It will make it easier to add some of the features I want in version 2.0 sometime down the road.

I won't have a new build for a bit but the updated decls file and dll are here...

http://www.outergods.com/blitz/blitzdataupd.zip

Kanati


Wayne(Posted 2004) [#2]
Oh Yes!


Kanati(Posted 2004) [#3]
it's all your fault too Wayne. :)


Wayne(Posted 2004) [#4]
Don't I know it.
8P

As much as I like the terminology of:

BD_SetQueryTimeout()
BD_GetQueryTimeout()

Do you suppose we should consider using the ADO terminology?
Something like this:

BD_SetCommandTimeout()
BD_GetCommandTimeout()

What do you think?

ps. Blitzdata is working sweet.


Kanati(Posted 2004) [#5]
hrm... I think I'll stick with QueryTimeout since it's for the query... Though it works for the BD_SQLCommand as well. It was really put in there for the query timeout even tho it works for both.

I'll take it under advisement tho. Just don't want to confuse people since there's a "command" command as well.

Maybe just BD_SetTimeout() and BD_GetTimeout()...........

Kanati


Wayne(Posted 2004) [#6]
lets keep:
BD_SetQueryTimeout()
BD_GetQueryTimeout()

I'll test some more tomorrow make sure things are working great.
Looks like your ready to publish it.
8)


Wayne(Posted 2004) [#7]
Hi Kanati,
Null numeric fields returned from query causes BD_GetColumn to FAIL.

Please add this:
BD_IsNull("ColumnName") Returns True/False
BD_IsNull(Ordinal%) Returns True/False

And Possibly something like this for lazy people to set default null values:
BD_SetAlphaNull("*NULL*")
BD_SetNumericNull(0)


Thank ye

Inspected by #9
8)


Kanati(Posted 2004) [#8]
I'll definitely look into this. Thanks.


Kanati(Posted 2004) [#9]
I didn't add any new commands... Really trying to avoid that now. Have to shut the thing down at some point or it'll never be "finished."

What I did do is make sure that BD_GetColumn() returns "*NULL*" if the column is null. Whether the column is text or numeric.

Also, I added three constants to the BD_Constants.bb file.

BD_NullString
BD_NullInt
BD_NullFloat


If you want to set a column to null, use the normal commands and pass the above constants as values. The column SHOULD be null. I tested this quickly with an access database and it appears to work fine.

www.outergods.com/blitz/blitzdataupd.zip

Let me know if there's any problems with it.

I plan to have a "release" tomorrow or wednesday unless I hear of any more problems. :)

Kanati


Wayne(Posted 2004) [#10]
Kanati,
This final, last request, would make it mint.

BD_IsNull("ColumnName") Returns True/False
BD_IsNull(Ordinal%) Returns True/False

my last request, I promise *mostly*

8)


Wayne(Posted 2004) [#11]
Kanati,
It would be cool to support parameterized queries.
Just think no concatinating to build up your big bad query.
8)

It's so nice to be able to set the parameters and run the query like:

BD_SetParm("DBAcct",AlphaType)="0000007"
BD_SetParm("DBAge",NumericType)="12"

t=BD_SQLQuery("select * from accounts where account=<%DBAcct|'0000000'%> and age> <%DBAge|10%>")

All you have to do is parse for <% %>, and plug in the value for parameter,
if none is provided use the default value of zeros in this case. SQL becomes:
select * from accounts where account='0000007' and age>12

<%DBAcct|'0000000'%>
shows parm name | default value

Just thought I'd get my LAST request in.
8)


Kanati(Posted 2004) [#12]
sigh... always wanting more... :)

I like it. I'll take a look at doing that tonight.

Kanati


Wayne(Posted 2004) [#13]
I find Blitzdata very functional at this point, every little bit at this point is gravy


Wayne(Posted 2004) [#14]
BD_GetColumn()
Returning *NULL* for valid numeric values.
Looks like when first record gets a null then it decides all future values will return null too.

help.
8)


Wayne(Posted 2004) [#15]
BLITZDATA NULL PROCESSING IS BROKEN

After some testing I believe the following is happening:
1. columns with empty strings are returning *NULL*
2. Numeric fields with value one are also returning *NULL*

Summary: I'd like to get rid of returning *NULL* stuff and let the programmer handle nulls in the query, and provide the blitz programmer a way to detect nulls from Blitz3d and deal with them.

BD_IsNull("ColumnName") Returns True/False
BD_IsNull(Ordinal%) Returns True/False

-Wayner


Kanati(Posted 2004) [#16]
I will look into this today.


Wayne(Posted 2004) [#17]
1. Columns with empty strings are returning *NULL*
2. Numeric fields with value one are also returning *NULL*

These are the main issues.


Kanati(Posted 2004) [#18]
I've got the laptop open and working on it right now. Going to finish up the docs and do a real release tonight or tomorrow.