SV: Databases, about vstudio 5.0

[ExcelKB]

Behind the large RDMS on the Microsoft platform it exist a growing
type of embedded dbs like VistaDB and Ninja Pro. The coming new
compact edition of SQL Server, SSCE, is an indicator that Microsoft
also pay attention to embedded dbs. If You ever had used LINQ it's
difficult to go back to SQL...

So once You have incorporated the major dragons it's time to set focus
on embedded dbs. In other words; back to work :-)

Thanks,
Dennis

-----Ursprungligt meddelande-----
Från: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] För Ruslan Zasukhin
Skickat: den 14 januari 2012 11:06
Till: valentina at lists.macserve.net
Ämne: Re: Databases, about vstudio 5.0

On 1/14/12 11:42 AM, "Beatrix Willius" <bwillius at gmx.de> wrote:

> On 14.01.2012, at 09:57, Ruslan Zasukhin wrote:
> 
> On 1/14/12 8:06 AM, "Beatrix Willius" <bwillius at gmx.de> wrote:
> 
> This is great news! You just saved me weeks and weeks of work.
> 
> About?
> 
> PostGres, of course. Not many people have heard about Valentina. And
I 
> have been thinking a bit about cheating on Valentina.

Well, logic of these our steps was during last few years

* Valentina Reports


* then we decide that Report Tool of course should support as much
datasources as possible. Sowe have add ODBC, Lite and now Postgre.

Future yet mySQL, may be MS SQL, others ... Btw in QT present it seems
good layer wrapper over set of dbs ... So may be when we switch to QT,
we almost automatically will get a lots of dbs in NATIVE way for
reports.


* When we have start add datasources, we have realize that we self
need open SqlLite db to see what is there, check Queries.

    So we have decide that it can be good idea if Vstudio self offer
also ability to browse that third party dbs ...

    Also we of course will try to add for all that dbs ONE CLICK
transfer into Valentina DB.


* And of course we have dream long time about powerful modeling.
Finally we have come to it .. OF course a lots of job here ... Than
more that we need provide three branches of code for each db.


* Also I should say it is interesting to learn soo deeply third party
dbs.
We have found few miss-parts in Valentina DB and have fix that, e.g.
CHECK now is more correct.

Also now we try add UNIQUE on few fields for Valentina DB. Not sure if
it will be in time for 5.0 ... But we work on it now.


==================
Also last days, once again I have spend hours to read inet all about
Primary Keys, and Foreign Keys for mySQL, Postgre, Light, Access, ...

And I have remember once again, why yet 15 years ago I have told self
--- I HATE THEM :)

On inet most people same the same... DO NOT USE THEM

So now, we have decide for self:
    yes we will support compound keys for UNIQUE constraint.
    it can be helpful in some cases.

    But we will NOT add into Valentina PK/FK on few fields.
    This is bad design.


=================
And yes,  as we see it, from  5.0

Valentina Studio can become absolutely standalone product, With new
target groups

A) REPORT Designer -- SQLite, Postgre, Valentina DB users can use it
B) DB Designer -- again for that 3 engines.

Yes, in such way, we can try promote Valentina Studio to new
developers.

This can be similar like Apple have jump to Windows world with iTunes,
Safari, iPod, iPhone ...




--
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information http://www.paradigmasoft.com

[I feel the need: the need for speed]


_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina


----------------------------------------------------------------------
-----------------------------
Text infogad av Panda GP 2011:

 Om detta dr ovnskad e-post (SPAM) klickar du pe fvljande ldnk fvr att
klassificera om meddelandet:
http://localhost:6083/Panda?ID=pav_8157&SPAM=true&path=C:\Windows\syst
em32\config\systemprofile\AppData\Local\Panda%20Security\Panda%20Globa
l%20Protection%202011\AntiSpam
----------------------------------------------------------------------
-----------------------------