FlameRobin

Lester Caine wrote:
> Having been using IBOConsole for a long time now, I've got used to some 
> aspects of it ( and IB_SQL before it ). While I keep a log of which version of 
> a database is running on a site, I always cross check by downloading a copy of 
> the site data and extracting the metadata prior to running any update checks. 
> This is easy in IBOConsole, and I can do a compare between the generated text 
> file and the current master metadata.
> 
> Can I do a full metadata extract in FlameRobin? I can see the single entry 
> stuff, but I can't see an 'extract all' :(

OK - As soon as I went back to have another play I found the right DDL link ;)
Funny how writing something down helps solve the problem yourself :)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

On Dec 17, 2007 9:57 AM, Lester Caine <lester@...> wrote:
> > Can I do a full metadata extract in FlameRobin? I can see the single entry
> > stuff, but I can't see an 'extract all' :(
>
> OK - As soon as I went back to have another play I found the right DDL link ;)
> Funny how writing something down helps solve the problem yourself :)

There were other people complaining about this before, so there's two
ways to get it:

1. Database properties page -> DDL

or

2. From the main menu, select:

Database -> Advanced -> Extract metadata DDL


-- 
Milan Babuskov
http://www.flamerobin.org

Milan Babuskov wrote:
> On Dec 17, 2007 9:57 AM, Lester Caine <lester@...> wrote:
>>> Can I do a full metadata extract in FlameRobin? I can see the single entry
>>> stuff, but I can't see an 'extract all' :(
>> OK - As soon as I went back to have another play I found the right DDL link ;)
>> Funny how writing something down helps solve the problem yourself :)
> 
> There were other people complaining about this before, so there's two
> ways to get it:
> 
> 1. Database properties page -> DDL

That is the one I found ;)

> or
> 
> 2. From the main menu, select:
> 
> Database -> Advanced -> Extract metadata DDL

Not on 0.8.1 -
I only get
- Show connected users
- Monitor Events
- Database Preferences
- Test Data Generator

But it would be useful if that was added and went STRAIGHT to the SQL editor. 
Having to open the DLL view and then scan again to get to a page where you can 
save the results is a pain - especially using a Linux server ( I'll post about 
that separately on firebird support ! ).

One last niggle with the DLL extract. *PLEASE* can we have SQL standard upper 
case for every reserved word. This knobbled 'Integer' and the like is an utter 
pain when every script is in upper case. I know it's just nit picking, but 
it's the same problem as forcing double quotes. There needs to be an option to 
give an SQL standard output.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

Hi,

On 17.12.2007 21:01 Lester Caine wrote:

> One last niggle with the DLL extract. *PLEASE* can we have SQL
> standard upper case for every reserved word. This knobbled 'Integer'
> and the like is an utter pain when every script is in upper case. I
> know it's just nit picking, but it's the same problem as forcing
> double quotes. There needs to be an option to give an SQL standard
> output.

that's something I have been thinking about lately.  I dislike the 
CamelCase data types too, and there are surely preferences for upper or 
lower case reserved words vs. upper or lower case identifiers and so on 
for everyone of us.

I think we need something like a StatementBuilder class, which is used 
everywhere the statements are built "manually" now.  That would be a 
central place to format statements according to user preferences.  It 
should also line-wrap statements at the column that's set at "Show long 
line marker" preference setting.  Probably more...

Thanks

-- 
Michael Hieke

On Dec 17, 2007 9:01 PM, Lester Caine <lester@...> wrote:
> > 2. From the main menu, select:
> >
> > Database -> Advanced -> Extract metadata DDL
>
> Not on 0.8.1 -

I guess we should do a new release soon. (You could try the snapshot
builds, but I guess that the fact that there are no RPMs is a
showstopper for you)

> But it would be useful if that was added and went STRAIGHT to the SQL editor.

Yes, that's exactly how it works.


-- 
Milan Babuskov
http://www.flamerobin.org

Michael Hieke wrote:
> Hi,
> 
> On 17.12.2007 21:01 Lester Caine wrote:
> 
>> One last niggle with the DLL extract. *PLEASE* can we have SQL
>> standard upper case for every reserved word. This knobbled 'Integer'
>> and the like is an utter pain when every script is in upper case. I
>> know it's just nit picking, but it's the same problem as forcing
>> double quotes. There needs to be an option to give an SQL standard
>> output.
> 
> that's something I have been thinking about lately.  I dislike the 
> CamelCase data types too, and there are surely preferences for upper or 
> lower case reserved words vs. upper or lower case identifiers and so on 
> for everyone of us.
> 
> I think we need something like a StatementBuilder class, which is used 
> everywhere the statements are built "manually" now.  That would be a 
> central place to format statements according to user preferences.  It 
> should also line-wrap statements at the column that's set at "Show long 
> line marker" preference setting.  Probably more...

I *DID* think Firebird returned upper case? So there should be no need to 
change anything in my case. If FIREBIRD is screwing around with the case of 
the DDL returns, then I'll register a bug there! I don't want that being 
buggered up :)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

On Dec 17, 2007 11:35 PM, Lester Caine <lester@...> wrote:
> I *DID* think Firebird returned upper case? So there should be no need to
> change anything in my case.

Actually, Firebird returns an integer, which we convert to datatype
name. For example, 14 means Char, 37 Varchar, 10 Float, etc. Some
numbers map to multiple 'names' depending on precision and other info.

-- 
Milan Babuskov
http://www.flamerobin.org

Milan Babuskov wrote:
> On Dec 17, 2007 11:35 PM, Lester Caine <lester@...> wrote:
>> I *DID* think Firebird returned upper case? So there should be no need to
>> change anything in my case.
> 
> Actually, Firebird returns an integer, which we convert to datatype
> name. For example, 14 means Char, 37 Varchar, 10 Float, etc. Some
> numbers map to multiple 'names' depending on precision and other info.

So just need to do my own build with an proper upper case table :)
IB_SQL and IBOConsole both return upper case so one gets used to it ;)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

On Dec 17, 2007 11:46 PM, Lester Caine <lester@...> wrote:
> So just need to do my own build with an proper upper case table :)

Well, if you really want to, it's all in src/metadata/domain.cpp  :)

> IB_SQL and IBOConsole both return upper case so one gets used to it ;)

I guess we need to do what Michael suggested and make it an option
that users can modify themselves.

-- 
Milan Babuskov
http://www.flamerobin.org

Milan Babuskov wrote:
> On Dec 17, 2007 11:46 PM, Lester Caine <lester@...> wrote:
>> So just need to do my own build with an proper upper case table :)
> 
> Well, if you really want to, it's all in src/metadata/domain.cpp  :)
> 
>> IB_SQL and IBOConsole both return upper case so one gets used to it ;)
> 
> I guess we need to do what Michael suggested and make it an option
> that users can modify themselves.

We have agreement on the projects I work with that all SQL is upper case and 
then we can switch between ADOdb engines transparently. So I'm loathed to have 
stuff floating around that breaks the rules.
CamelCase is not standard for SQL so should not be a default ;)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

Milan,

M> I guess we need to do what Michael suggested and make it an option
M> that users can modify themselves.

Yes, we talked about that in the past but it was long ago. Personally
I would like names upper case and everything else lowercase. ;-)

Maybe we probably get around it by using templates stored externally. A
configuration option would indicate the template directory to use.
Templates would need to be recursive (i.e. a template could contain
references to other templates). They coiuld be modeled in a similar
way as the BNF diagrams for the SQL statements. The statement builder
would load and expand templates when it comes to building a statement
or part of it.

Ciao
-- 
Nando Dessena

On Dec 18, 2007 1:09 AM, Lester Caine <lester@...> wrote:
> CamelCase is not standard for SQL so should not be a default ;)

FWIW, there's no Camel Case in FR :)

Types are named with initial capital letter. Technically, this is the
subset of Camel Case convention, but that was not the intention.
Anyway, I don't have some preference about this (I write very clear
PSQL and DDL code and usually have only one datatype on the line at
any time, so there's no way to get confused - not to mention that the
editor highlights it).

That being said, I won't mind if anyone adds code formatting to FR,
and I'll change the code that I wrote to use it accordingly. However,
I don't have it in my plans yet - there are other more important
issues and not much free time.

-- 
Milan Babuskov
http://www.flamerobin.org

Milan Babuskov wrote:
> On Dec 18, 2007 1:09 AM, Lester Caine <lester@...> wrote:
>> CamelCase is not standard for SQL so should not be a default ;)
> 
> FWIW, there's no Camel Case in FR :)
> 
> Types are named with initial capital letter. Technically, this is the
> subset of Camel Case convention, but that was not the intention.

You are right - I just class anything with Capital first letter as CamelCase 
as that is what the purists seem to expect with single word Identifiers ( 
should it be VarChar for Camel case :) )

> Anyway, I don't have some preference about this (I write very clear
> PSQL and DDL code and usually have only one datatype on the line at
> any time, so there's no way to get confused - not to mention that the
> editor highlights it).
> 
> That being said, I won't mind if anyone adds code formatting to FR,
> and I'll change the code that I wrote to use it accordingly. However,
> I don't have it in my plans yet - there are other more important
> issues and not much free time.

I've no intention to try and build my own copy on Windows, I only have BCB5/6 
compilers, but the Linux box should be able to handle it?  :)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

On Dec 18, 2007 9:36 AM, Lester Caine <lester@...> wrote:
> I've no intention to try and build my own copy on Windows, I only have BCB5/6
> compilers, but the Linux box should be able to handle it?  :)

Yes. I develop FR on Linux. In fact, I don't even have Windows installed.


-- 
Milan Babuskov
http://www.flamerobin.org

Nando Dessena wrote:

> Personally I would like names upper case and everything else
> lowercase. ;-)

+1

> Maybe we probably get around it by using templates stored externally.
> A configuration option would indicate the template directory to use. 
> Templates would need to be recursive (i.e. a template could contain 
> references to other templates). They coiuld be modeled in a similar 
> way as the BNF diagrams for the SQL statements. The statement builder
> would load and expand templates when it comes to building a
> statement or part of it.

IMHO the questions of a code formatter class and templates are 
orthogonal; both would probably make sense, but are not really 
replacements for the other.  There are places where templates simply 
don't make sense (drag and drop query building comes to mind).

Thanks

-- 
Michael Hieke