Icon View Thread

The following is the text of the current message along with any replies.
Messages 51 to 59 of 59 total
Thread ElevateDB on Compact Framework
Fri, Jul 18 2008 2:44 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< As I remember  UTF8 is used all over at Lazarus. FPC is still using ANSI.
>>

Yes, but they do have proper WideString support.  It's just that the
implicit conversions from AnsiString <--> WideString don't seem to be
working correctly.  It looks like they're doing a one-to-one byte conversion
when converting WideStrings to AnsiStrings so that the AnsiStrings end up
having twice as many characters and a bunch of non-printable characters in
them.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jul 18 2008 3:14 PMPermanent Link

Leslie
Tim,

"Yes, but they do have proper WideString support.  It's just that the
implicit conversions from AnsiString <--> WideString don't seem to be
working correctly.  It looks like they're doing a one-to-one byte conversion
when converting WideStrings to AnsiStrings so that the AnsiStrings end up
having twice as many characters and a bunch of non-printable characters in
them."


You can ask your questions on the Lazarus mailing list. It may save you some valuable time.
(http://www.lazarus.freepascal.org/modules.php?op=modload&name=StaticPage&file=index&sURL=maill)

Have you tried the ANSI version of ElevateDB too? Maybe there are less problems there. ((:
Or maybe more. Smile
TBH my first choise would be the later, becuse of the very limited memory on PDA's.

Leslie
Fri, Jul 18 2008 3:23 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< You can ask your questions on the Lazarus mailing list. It may save you
some valuable time.
(http://www.lazarus.freepascal.org/modules.php?op=modload&name=StaticPage&file=index&sURL=maill)>>I will do once I do a quick run-through the source code.  I want to makesure that my idea about what is happening is correct.<< Have you tried the ANSI version of ElevateDB too? Maybe there are lessproblems there. ((: Or maybe more. Smile TBH my first choise would be the later, becuse of the very limited memoryon PDA's. >>Windows CE only does Unicode (W versions of the Windows API), so ANSI is outof the question.  However, the ANSI version of ElevateDB works great onnormal Windows/FP.--Tim YoungElevate Softwarewww.elevatesoft.com
Fri, Jul 18 2008 3:26 PMPermanent Link

Leslie
Tim,

"Windows CE only does Unicode (W versions of the Windows API), so ANSI is outof the
question.  However, the ANSI version of ElevateDB works great onnormal Windows/FP."

Clear. Thank you.

Leslie
Fri, Jul 18 2008 3:39 PMPermanent Link

Leslie
"The ANSI version of ElevateDB works great onnormal Windows/FP.""

I suppose if there is a mix of ANSI and Unicode servers, then replication needs to be done
by the user between the the the two type of servers?

Leslie
Fri, Jul 18 2008 4:10 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< I suppose if there is a mix of ANSI and Unicode servers, then replication
needs to be done by the user between the the the two type of servers? >>

You can't mix ANSI with Unicode in EDB at all.  Everything is done as one or
the other.  If you're doing replication, then all involved parties in the
replication must use the same EDB type.   For example, when EDB is Unicode,
the update file generated by the SAVE UPDATES statement is entirely Unicode,
so it can only be used with a LOAD UPDATES statement on a Unicode version of
EDB.

Eventually this will all be a non-issue since everything will work as
Unicode, but for now it's the source for more than a little confusion. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jul 18 2008 4:53 PMPermanent Link

Leslie
Tim,

"You can't mix ANSI with Unicode in EDB at all."

I have replication developed for an other DB engine which probably can be applied for
ElevateDB.  Character encoding conversation fits into it easily, so it would make mixing
different servers possible. This is what I have meant by "by the user" . But I will leave
the replication issue now.  Would not want to keep you occupied "chating" with me instead
of doing the more important things.       


Thank you,
Leslie
Fri, Jul 18 2008 4:59 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< I have replication developed for an other DB engine which probably can be
applied for ElevateDB.  Character encoding conversation fits into it easily,
so it would make mixing different servers possible. This is what I have
meant by "by the user" . But I will leave the replication issue now. >>

Ahh, yes, in that case it would work just fine.

<< Would not want to keep you occupied "chating" with me instead of doing
the more important things. >>

Not a problem.  I check this stuff while I'm compiling, etc. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jul 18 2008 8:37 PMPermanent Link

"Julio S."
Tim Young [Elevate Software] escribió:
> Leslie,
>
> Here's a screen shot of ElevateDB running in a test app in the Lazarus IDE:
>
> http://www.elevatesoft.com/edblazaruswin.png
>

Nice Smile
« Previous PagePage 6 of 6
Jump to Page:  1 2 3 4 5 6
Image