Your 3 DREAM FEATURE for Vstudio ?

[Jochen Peters]

Hi Ruslan,

which encoding is used when we create a I_Disk_Location via method  
CreateDiskLocation ?
(This location build from the path of the SQL file is passed to the  
LoadDump method)


Am 20.06.2005 um 21:33 schrieb Heinrich Ruoff:

> Which text encoding is currently required to load external sql files?
>
> Heinrich
>
> On 6/19/05, Jochen Peters <j.peters at valentina-db.de> wrote:
>
>>> On 6/18/05, Ruslan Zasukhin <sunshine at public.kherson.ua> wrote:
>>>
>>>> On 6/18/05 3:25 PM, "Heinrich Ruoff" <heinrichruoff at gmail.com>  
>>>> wrote:
>>>>
>>>>
>>>>> ok got it - Load SQL only works when there is a Database already
>>>>>
>>>> opened
>>>>
>>>> Jochen, I believe this is not correct.
>>>>
>>>> LoadSQL -- do not require existed Valentina db. It create new  
>>>> fresh.
>>>>     so dialog must ASK user where to put new db.
>>>>
>>>
>>> with Valentina Studio 2.0b8 nothing happens pressing Load SQL
>>> when no DB is already opened
>>> thats why I thought the feature is not implemented yet
>>>
>> Yes - this is bug! Load SQL should work without a current  
>> database. We
>> will change that
>> for the next release.
>>
>>
>>>
>>>
>>>>
>>>>
>>>>> but it doesn't seem to work with my .sql file created for mySQL
>>>>>
>>>>
>>>> Is this file in the UTF8 ?
>>>>
>>>
>>> it is UTF8
>>>
>>>
>>>>
>>>> Then yes, Jochen should add parameter ENCODING for this dialog.
>>>>
>>>>
>>>>
>>>>> is there an option to import .sql files to an existing  
>>>>> Valentina DB?
>>>>> Load SQL always asks for a new filename
>>>>>
>>>>
>>>> Into existing .... We have such option for XML load...
>>>>
>>>> For SQL not remember. Does mySQL allow such operation ?
>>>> In the LoadDump() method we have parameter
>>>>
>>>>     kStructureAndData, kDataOnly, kStructureOnly.
>>>>
>>>> I do not see problems implement that if you point kDataOnly,
>>>> Then just ignore CREATE TABLE commands, and execute only inserts...
>>>>
>>>> -----
>>>> Aha, I have remember one point.
>>>>
>>>> For Relational model it can be danger import into EXISTED db that
>>>> already
>>>> have records, because you can get not-unique kees or Forein keys...
>>>>
>>>> You see?
>>>>
>>>
>>> ok - makes sense
>>> it would not be a problem for my current project
>>> to load everything instead of just the changes
>>>
>>> Heinrich
>>> _______________________________________________
>>> Valentina-beta mailing list
>>> Valentina-beta at lists.macserve.net
>>> http://lists.macserve.net/mailman/listinfo/valentina-beta
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Jochen Peters
>> PIIT GmbH
>>
>> --------------------------
>> http://www.valentina-db.de
>> _______________________________________________
>> Valentina-beta mailing list
>> Valentina-beta at lists.macserve.net
>> http://lists.macserve.net/mailman/listinfo/valentina-beta
>>
>>
> _______________________________________________
> Valentina-beta mailing list
> Valentina-beta at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina-beta
>
>



-- 
Best regards,
Jochen Peters
PIIT GmbH

------------------------------------
http://www.valentina-db.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macserve.net/pipermail/valentina-beta/attachments/20050620/9787ac89/attachment.html