Open GoogleCodeExporter opened 9 years ago
I vote for Firebird because it is probably the most widely used DB among these,
and
is feature-rich. And it can be also used in client-server mode.
Original comment by havasvol...@gmail.com
on 3 Dec 2009 at 4:40
Vote for firebird also
Original comment by psu...@gmail.com
on 1 Jan 2010 at 9:11
We consider SQL Server CE as well. So we'll start from evaluating possibility
to
support it first, and later switch to alternatives.
Original comment by alex.yakunin
on 3 Jan 2010 at 5:32
I think supporting SQL Server CE before supporting other SQL engine is not good
option, because you have already support for "BIG" SQL Server already. Users
which
not select SQL from M$ can select other SQL engine like Firebird.
Just my 2 cents.
Original comment by psu...@gmail.com
on 4 Jan 2010 at 8:19
Adding support for SQL Server CE is a simplier task because CE generally shares
T-SQL
dialect with "big" SQL Server. This dialect is already well-supported by our
Sql engine.
Original comment by denis.kr...@gmail.com
on 5 Jan 2010 at 9:38
I know it is simplier to support CE. But i post my opinoin to support other
than M$
sql product, like Firebird.
Original comment by psu...@gmail.com
on 5 Jan 2010 at 11:11
I agree alternatives must be supported. Our initial goal was to support "big 4"
databases: Oracle, SQL Server, MySQL (still undone) and PostgreSQL. Together
they
share 95-98% of the market. So as you see, we're trying to support all hte
major
"camps" there.
But since now customers require support of embedded databases, we're looking
for the:
a) fastest way to support the first one there. SQL CE & VistaDB are the most
probable
candidates here.
b) fastest way to support the second one from alternative camp. E.g. if the
first one
will be SQL CE, the second one must be Firebird (free).
c) finally we should deliver our own embedded DB. But as you know, we decided
to
implement all the major stuff customers expect from us, which is not depended
to any
database, before returning back to this part of DO4.
Original comment by alex.yakunin
on 5 Jan 2010 at 12:02
I need support for an embedded database. As long as it is fast and stable, I
don't
really care very much which one it is. My previous experience with Firebird
embedded
is not only positive regarding stability, but the bugs might be fixed in the
later
versions. The fact that VistaDB is written completely in .NET is plus for me.
Original comment by t...@faktum.co
on 14 Jan 2010 at 9:11
Returnad back to v4.1.
Dmitry, please add some comments on existing SQL CE provider.
Original comment by alex.yakunin
on 8 Feb 2010 at 8:26
Sql Server CE provider is fully working except minor features:
- optional parameters in connectionUrl are not taken into account when
connection
string is being constructed.
- as CE doesn't support RowNumber function or its analogue, an appropriate
workaround should be invented, if possible.
Original comment by Dmitri.Maximov
on 8 Feb 2010 at 9:20
Original comment by alexis.k...@gmail.com
on 9 Feb 2010 at 1:43
Partially Done. Sql Server CE Beta support
Original comment by alexis.k...@gmail.com
on 9 Feb 2010 at 2:21
Issue 561 has been merged into this issue.
Original comment by denis.kr...@gmail.com
on 11 Feb 2010 at 12:14
Definitely vote for Firebird. Firebird is widely used and has wide adoption as
an
embedded database in a large number of commercial applications. Firebird
supports
array datatypes, blob filters, real time event alerters, mult-version
concurrency
control, etc, etc.
Original comment by ldsmithp...@gmail.com
on 14 Apr 2010 at 10:35
Original issue reported on code.google.com by
alex.yakunin
on 2 Dec 2009 at 11:37