BTW do you think, that prefix should be each for every provider or same
for all ASP.NET web providers?
I vote for same.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
This SF.net email is
Hi,
Presently our windows application is on .Net 1.2 and Firebird 2.0
environment. We are planning to upgrade our .Net environment to 2.0.
Please let me know if any show stoppers.
Thanks,
-Ram
-
This SF.net email is
Hello:
I have updated yesterday the Wix installer sources in the svn trunk.
It looks as working while it provides only basic funcionality :)
Hope to improve it a little over the next days.
--
Un saludo
Carlos Guzmán Álvarez
Vigo-Spain
http://carlosga.wordpress.com
--
Hello:
> Ok. Seems my english is quite bad :-)
Maybe using the Native term isn't as accurate as it could be but, as
the pure C# GDS implementations are under the Managed namespace i think
it's clear enough ;)
-
This SF.net e
Hello:
> What do you think?
Looks fine to me
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
> No, native means that it will use some "native" firebird client dll
> (fbembedded, fnclient, gds32, ... )
Ok. Seems my english is quite bad :-)
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the
le roy arnaud wrote:
>>> So I propose MP$SOMETHING
>>
>> Looks good, too.
>>
>
> Yes so for tables :
>
> MemberShip Proprider : MP$
> Role Provider : RP$
> Profile Provider : PP$
>
> and the same for proc ?
OK. Ill update names with creating FB2.0 scripts.
--
Jiri {x2} Cincura
http://blog.v
Hello:
> Thought about this. Can i understand that "native" related to .NET
> provider, i.e. implemented inside of provider?
No, native means that it will use some "native" firebird client dll
(fbembedded, fnclient, gds32, ... )
-
Hello:
> No, that is one byte that is being communicated while establishing the
> connection. IB 5.x had wire protocol version 9, IB 6.x, FB 1.x, FB 2.0,
> IB 7.x (and very likely IB 2007) have protocol version 10. FB 2.1
> supports protocol versions 10 and 11.
>
> Client talking wire protocol
>> So I propose MP$SOMETHING
>
> Looks good, too.
>
Yes so for tables :
MemberShip Proprider : MP$
Role Provider : RP$
Profile Provider : PP$
and the same for proc ?
-
This SF.net email is sponsored by DB2 Express
Downl
> No, that is one byte that is being communicated while establishing the
> connection. IB 5.x had wire protocol version 9, IB 6.x, FB 1.x, FB 2.0,
> IB 7.x (and very likely IB 2007) have protocol version 10. FB 2.1
> supports protocol versions 10 and 11.
>
> Client talking wire protocol 10 is n
>>> What is version 10 ? Maby Version_1, Version_2, ets... ?
>> It's the version of FB Protocol. AFAIK.
>
> It's impossible. Newest Interbase server has version 8 and protocol
> didn't change in each version, so protocol version can't be greater than
> server version. So i think that "version
> Not ODS, but GDS (the protocol version wasn't the right term).
Ok, than what GDS has FB 1.0 and FB 1.5 ?
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
co
sasha wrote:
>>> What is version 10 ? Maby Version_1, Version_2, ets... ?
>>
>> It's the version of FB Protocol. AFAIK.
>
> It's impossible. Newest Interbase server has version 8 and protocol
> didn't change in each version, so protocol version can't be greater than
> server version. So i thi
>> What is version 10 ? Maby Version_1, Version_2, ets... ?
>
> It's the version of FB Protocol. AFAIK.
It's impossible. Newest Interbase server has version 8 and protocol
didn't change in each version, so protocol version can't be greater than
server version. So i think that "version 10" sou
sasha wrote:
> So I propose MP$SOMETHING
Looks good, too.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE vers
le roy arnaud wrote:
> Hi Jiri,
>
> first i think that we should do the script for the firebird 2.0 .
I'm working on it.
>
>>
>> I'm thinking about adding some prefix to SQL scripts for creating
>> tables, etc. for membershipshiping.
>>
>
>
>
>> Why to do this.
>>First there's some inconsist
> 2.
>
> FirebirdSql.Data.Client.Embedded -> FirebirdSql.Data.Client.Native
Thought about this. Can i understand that "native" related to .NET
provider, i.e. implemented inside of provider?
If so, than here is ambiguity and this is bad namespace and i propose
something like
FirebirdSql.Data.C
Hi Jiri,
first i think that we should do the script for the firebird 2.0 .
>
> I'm thinking about adding some prefix to SQL scripts for creating
> tables, etc. for membershipshiping.
>
> Why to do this.
>First there's some inconsistency in these scripts.
Where
> So this would help keep
> Ideas:
> * FB_something
> * FBMemebership_something
> * FBM_something
I think prefix should be:
1) Short
2) Contain $ (in IB/FB traditions)
3) I think prefix FB is unnecessary because it's clear without it
So I propose MP$SOMETHING
-
20 matches
Mail list logo
